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.
Widgets cannot be dragged back into an emptied bar section
Reported by james-engelbrecht · filed Sep 8, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #9842 (R-1043). GitHub close reason: completed.
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
AMD Ryzen 7 5800H, NVIDIA RTX 3060 Mobile, Omarchy 4.0.2-1, kernel 7.1.9-arch1-2, quickshell 0.3.1
What's wrong?
A bar widget can be dragged out of a bar section, but once the section is empty it can never be dragged back into it — the drop is silently ignored.
Steps to reproduce
- Drag a widget (e.g. workspaces) out of the center section and drop it anywhere on the bar. The center section is now empty.
- Drag any widget back toward the emptied section and release.
- Nothing happens: the config is unchanged and the widget returns to where it came from.
Only omarchy bar move <id> --section <section> or a manual shell.json edit recovers the widget's position.
Cause
moduleDropAtScene (shell/plugins/bar/Bar.qml) collects drop candidates only from mapped ModuleSlots and skips slots with !slot.visible || slot.width <= 0 || slot.height <= 0. An emptied section renders only the zero-size invisible placeholder (emptyModuleComponent: Item { implicitWidth: 0; implicitHeight: 0; visible: false }), so no candidate exists for that region and nearestDropTarget can never select it.
The empty section is not gone from the layout — it still exists in shell.json — it just has no hit area during drags.
Suggested fix
Register an invisible, zero-input drop zone for a region while that region has no widgets. I have this working locally and will open a PR: an EmptySectionZone inline component that calls registerModuleSlot while layoutEntries(region).length === 0, placed at the region's logical spot (bar edges and center, for both horizontal and vertical bars), with moduleName: "" so a drop appends to the section. It hides itself automatically once the section is populated, leaving all existing drag behavior untouched.
View raw text
### System details
AMD Ryzen 7 5800H, NVIDIA RTX 3060 Mobile, Omarchy 4.0.2-1, kernel 7.1.9-arch1-2, quickshell 0.3.1
### What's wrong?
A bar widget can be dragged *out* of a bar section, but once the section is empty it can never be dragged *back into* it — the drop is silently ignored.
**Steps to reproduce**
1. Drag a widget (e.g. workspaces) out of the center section and drop it anywhere on the bar. The center section is now empty.
2. Drag any widget back toward the emptied section and release.
3. Nothing happens: the config is unchanged and the widget returns to where it came from.
Only `omarchy bar move <id> --section <section>` or a manual shell.json edit recovers the widget's position.
**Cause**
`moduleDropAtScene` (shell/plugins/bar/Bar.qml) collects drop candidates only from mapped `ModuleSlot`s and skips slots with `!slot.visible || slot.width <= 0 || slot.height <= 0`. An emptied section renders only the zero-size invisible placeholder (`emptyModuleComponent: Item { implicitWidth: 0; implicitHeight: 0; visible: false }`), so no candidate exists for that region and `nearestDropTarget` can never select it.
The empty section is not gone from the layout — it still exists in shell.json — it just has no hit area during drags.
**Suggested fix**
Register an invisible, zero-input drop zone for a region while that region has no widgets. I have this working locally and will open a PR: an `EmptySectionZone` inline component that calls `registerModuleSlot` while `layoutEntries(region).length === 0`, placed at the region's logical spot (bar edges and center, for both horizontal and vertical bars), with `moduleName: ""` so a drop appends to the section. It hides itself automatically once the section is populated, leaving all existing drag behavior untouched.
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.