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.
Selected state drops the border on ToggleSwitch, MultiSelect and CursorSurface
Reported by relctx · filed Aug 28, 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
A ToggleSwitch has a border when off and none when on. The same happens to
MultiSelect items and CursorSurface when they become current.
selected-border-width defaults to 0 (Commons/Style.qml:79) whilenormal-border-width defaults to 1 (line 77). Button treats a zero
selected width as "no dedicated selected border" and falls back:
// Ui/Button.qml:108
: selected ? (Border.controlHasWidth("selected") ? _selectedBorderSpec
: (bordered ? _normalBorderSpec : Border.none()))with the intent stated just above it:
Selected borders are off by default for plain buttons; explicitly bordered buttons keep their normal border when selected unless selected-border-width opts in to a dedicated selected border.
Three other widgets switch to the selected spec with no such guard, so the
border goes to width 0 and disappears:
Ui/ToggleSwitch.qml:85— the track always setsborderSpec, so by
Button's wording it is an explicitly bordered control
- Ui/MultiSelect.qml:564
- Ui/CursorSurface.qml:33
Reproduce: open the Wi-Fi panel and toggle AUTOMATIC. Off has a 1px
border, on has none.
Themes inherit the default unless they override it.
Possible direction, untested: Button's guard applied to the others, roughly
borderSpec: Border.controlSpec(
root.checked && Border.controlHasWidth("selected") ? "selected" : "normal",
root.foreground, root.accent)CursorSurface has its own bordered property, which would need the same
handling Button gives it.
Omarchy 4.0.1-1, Quickshell 0.3.1.
View raw text
A ToggleSwitch has a border when off and none when on. The same happens to
MultiSelect items and CursorSurface when they become current.
`selected-border-width` defaults to 0 (`Commons/Style.qml:79`) while
`normal-border-width` defaults to 1 (line 77). `Button` treats a zero
selected width as "no dedicated selected border" and falls back:
```qml
// Ui/Button.qml:108
: selected ? (Border.controlHasWidth("selected") ? _selectedBorderSpec
: (bordered ? _normalBorderSpec : Border.none()))
```
with the intent stated just above it:
> Selected borders are off by default for plain buttons; explicitly bordered
> buttons keep their normal border when selected unless selected-border-width
> opts in to a dedicated selected border.
Three other widgets switch to the selected spec with no such guard, so the
border goes to width 0 and disappears:
- `Ui/ToggleSwitch.qml:85` — the track always sets `borderSpec`, so by
Button's wording it is an explicitly bordered control
- `Ui/MultiSelect.qml:564`
- `Ui/CursorSurface.qml:33`
**Reproduce:** open the Wi-Fi panel and toggle AUTOMATIC. Off has a 1px
border, on has none.
Themes inherit the default unless they override it.
**Possible direction, untested:** Button's guard applied to the others, roughly
```qml
borderSpec: Border.controlSpec(
root.checked && Border.controlHasWidth("selected") ? "selected" : "normal",
root.foreground, root.accent)
```
CursorSurface has its own `bordered` property, which would need the same
handling Button gives it.
Omarchy 4.0.1-1, Quickshell 0.3.1.
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 09:46 UTC