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.
[Regression] Floating window gets placed under Waybar after toggle (follow-up to #2822)
Reported by guidovicino · filed Nov 11, 2025Closed upstream on 2026-02-02 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Omarchy 3.1.7
What's wrong?
Summary
This appears to be a regression or an unhandled variant of the behavior discussed in #2822 (Omarchy) and #12139 (Hyprland)
After toggling a tiled window to floating, the window gets positioned under the top bar (Waybar), so part of it is hidden.
Prior context
- Related (closed): #2822
Steps to Reproduce
- Start a clean session with Waybar running at the top.
- Open a tiled window (e.g.,
ghostty, chromium). - Trigger the
togglefloatingdispatcher on the focused window. - Observe the window’s top edge intersecting with / being covered by the bar.
Expected Behavior
When toggling to floating, the window should be clamped within the visible area of the monitor (excluding the bar’s reserved/overlay area).
Actual Behavior
The window is clamped to the monitor bounds but ends up partially hidden under the top bar (Waybar).
Environment
- App/WM: Hyprland
v0.52.1(commit967c3c7404d4fa00234e29c70df3e263386d2597) - Monitors & scale:
< 2560x1440 @ 1.0>
Minimal Config to Reproduce
Hyprland
bindd = SUPER, T, Toggle window floating/tiling, togglefloatingAttached video
https://github.com/user-attachments/assets/dd448e81-90b3-4180-a718-6a15625289df
View raw text
### System details Omarchy 3.1.7 ### What's wrong? ### Summary This appears to be a regression or an unhandled variant of the behavior discussed in #2822 (Omarchy) and [#12139](https://github.com/hyprwm/Hyprland/pull/12139) (Hyprland) After toggling a tiled window to floating, the window gets positioned *under* the top bar (Waybar), so part of it is hidden. ### Prior context - Related (closed): #2822 ### Steps to Reproduce 1. Start a clean session with Waybar running at the top. 2. Open a tiled window (e.g., `ghostty, chromium`). 3. Trigger the `togglefloating` dispatcher on the focused window. 4. Observe the window’s top edge intersecting with / being covered by the bar. ### Expected Behavior When toggling to floating, the window should be clamped within the *visible* area of the monitor (excluding the bar’s reserved/overlay area). ### Actual Behavior The window is clamped to the monitor bounds but ends up partially hidden under the top bar (Waybar). ### Environment - App/WM: Hyprland `v0.52.1` (commit `967c3c7404d4fa00234e29c70df3e263386d2597`) - Monitors & scale: `< 2560x1440 @ 1.0>` ### Minimal Config to Reproduce **Hyprland** ```ini bindd = SUPER, T, Toggle window floating/tiling, togglefloating ``` ### Attached video https://github.com/user-attachments/assets/dd448e81-90b3-4180-a718-6a15625289df
- dd448e81-90b3-4180-a718-6a15625289df
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.
No decision has been recorded yet.