Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Microsoft Edge exposes extension popups and tooltips as anonymous Hyprland windows
Reported by AvrumFeldman · filed Aug 20, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
- Omarchy:
4.0.0-1 - Hyprland:
0.56.2-1(efb50993780079460b0cbed1363e2166a2de1d9f) - Aquamarine:
0.14.0-2 - Microsoft Edge:
151.0.4129.86-1 - Edge backend: native Wayland (
xwayland: falseinhyprctl clients) - GPU: Intel Iris Xe (
i915) - Display:
1920x1200, scale1
What's wrong?
Microsoft Edge exposes browser/extension UI as compositor-managed windows under native Wayland instead of keeping it as correctly anchored transient UI:
- A Bitwarden extension pop-out opens as a new pane in the Hyprland layout rather than as a compact popup at the top-right of the originating Edge window.
- Hovering controls in the Bitwarden extension UI creates a second tooltip as a short-lived anonymous Hyprland window. That window takes focus, which dismisses the originating extension popup. Edge itself does not crash.
The tooltip window is emitted on Hyprland's event socket with an empty class and title:
openwindow>><address>,1,,
activewindow>>,
activewindowv2>><address>
closewindow>><address>A screenshot captured after temporarily floating and suppressing focus on the anonymous window shows both tooltips simultaneously: the correctly anchored Edge tooltip beside the button and the erroneous OS-level tooltip elsewhere on screen.
Steps to reproduce
- Start Microsoft Edge using its native Wayland backend.
- Install/open the Bitwarden extension from Edge's toolbar.
- Hover a control that has a tooltip, such as Pop out to a new window.
- Observe a new anonymous Hyprland window/pane and the extension popup losing focus or closing.
- Open Bitwarden's pop-out window.
- Observe that it enters the layout as a pane instead of opening at a compact popup size near the originating browser.
Expected behavior
- Extension UI and its tooltips remain correctly anchored to the originating Edge window.
- Tooltips do not appear as separate Hyprland clients, alter the layout, or take focus.
- Bitwarden's pop-out opens at its requested compact size rather than as a pane.
Actual behavior
- The Bitwarden pop-out becomes a layout pane.
- A tooltip becomes a short-lived anonymous Hyprland window, takes focus, and dismisses the extension popup.
- Edge remains running; this is not a crash report.
Workarounds attempted
The following personal rules were added only after reproducing the original behavior:
- Matching Bitwarden's extension class and forcing
float,size = { 480, 630 }, and a top-right position restores the pop-out's usable geometry. - Matching anonymous native-Wayland windows (
class = "^$",title = "^$") can stop the tooltip from becoming a pane, but is unsafe: Edge also creates legitimate extension UI anonymously during startup, so the rule catches both and breaks Bitwarden's size, position, focus, or Escape behavior.
This means a general empty-class/title window rule is not a viable Omarchy workaround. The tooltip and legitimate extension UI need to be distinguishable, or the underlying Edge/Hyprland Wayland interaction needs to be corrected.
Additional information
- The problem occurs at display scale
1, so fractional scaling is not required. - No existing Omarchy issue was found for this non-crashing symptom. It differs from #5097, where Edge segfaults on hover.
- Standard diagnostic output was generated locally with
omarchy-debug --no-sudo --printand can be provided if needed.
View raw text
### System details
- Omarchy: `4.0.0-1`
- Hyprland: `0.56.2-1` (`efb50993780079460b0cbed1363e2166a2de1d9f`)
- Aquamarine: `0.14.0-2`
- Microsoft Edge: `151.0.4129.86-1`
- Edge backend: native Wayland (`xwayland: false` in `hyprctl clients`)
- GPU: Intel Iris Xe (`i915`)
- Display: `1920x1200`, scale `1`
### What's wrong?
Microsoft Edge exposes browser/extension UI as compositor-managed windows under native Wayland instead of keeping it as correctly anchored transient UI:
1. A Bitwarden extension pop-out opens as a new pane in the Hyprland layout rather than as a compact popup at the top-right of the originating Edge window.
2. Hovering controls in the Bitwarden extension UI creates a second tooltip as a short-lived anonymous Hyprland window. That window takes focus, which dismisses the originating extension popup. Edge itself does **not** crash.
The tooltip window is emitted on Hyprland's event socket with an empty class and title:
```text
openwindow>><address>,1,,
activewindow>>,
activewindowv2>><address>
closewindow>><address>
```
A screenshot captured after temporarily floating and suppressing focus on the anonymous window shows both tooltips simultaneously: the correctly anchored Edge tooltip beside the button and the erroneous OS-level tooltip elsewhere on screen.
### Steps to reproduce
1. Start Microsoft Edge using its native Wayland backend.
2. Install/open the Bitwarden extension from Edge's toolbar.
3. Hover a control that has a tooltip, such as **Pop out to a new window**.
4. Observe a new anonymous Hyprland window/pane and the extension popup losing focus or closing.
5. Open Bitwarden's pop-out window.
6. Observe that it enters the layout as a pane instead of opening at a compact popup size near the originating browser.
### Expected behavior
- Extension UI and its tooltips remain correctly anchored to the originating Edge window.
- Tooltips do not appear as separate Hyprland clients, alter the layout, or take focus.
- Bitwarden's pop-out opens at its requested compact size rather than as a pane.
### Actual behavior
- The Bitwarden pop-out becomes a layout pane.
- A tooltip becomes a short-lived anonymous Hyprland window, takes focus, and dismisses the extension popup.
- Edge remains running; this is not a crash report.
### Workarounds attempted
The following personal rules were added only **after** reproducing the original behavior:
- Matching Bitwarden's extension class and forcing `float`, `size = { 480, 630 }`, and a top-right position restores the pop-out's usable geometry.
- Matching anonymous native-Wayland windows (`class = "^$"`, `title = "^$"`) can stop the tooltip from becoming a pane, but is unsafe: Edge also creates legitimate extension UI anonymously during startup, so the rule catches both and breaks Bitwarden's size, position, focus, or Escape behavior.
This means a general empty-class/title window rule is not a viable Omarchy workaround. The tooltip and legitimate extension UI need to be distinguishable, or the underlying Edge/Hyprland Wayland interaction needs to be corrected.
### Additional information
- The problem occurs at display scale `1`, so fractional scaling is not required.
- No existing Omarchy issue was found for this non-crashing symptom. It differs from #5097, where Edge segfaults on hover.
- Standard diagnostic output was generated locally with `omarchy-debug --no-sudo --print` and can be provided if needed.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 04:55 UTC