Dialogs and confirmation
System confirmation keeps a consequential operation in the surface where it started.
Current beta & runtime boundary
At snapshot 6e6ad828c (2026-11-02 canonical ledger), 19 of 242 whole EARS requirements and 42 of 417 scenarios hold historical source-bound acceptance (ELM-TEA-001, ELM-TEA-002, and ELM-DEL-010, alongside published a327c8f7f Store and 6e6ad828c persistent custody CPU checks). The embedded desktop specimen below runs in-browser over deterministic fixtures, and captures in Evidence come from the frozen bc3daf7b reference baseline. Native Omarchy/Hyprland GUI, provider cleanup, AT/IME, hardware latency, and release acceptance for this surface remain OPEN.
Overview
System confirmation keeps a consequential operation in the surface where it started.
Anatomy
The inline confirmation contains the consequence, Cancel and Confirm, in that order. Cancel receives initial focus. It has no modal scrim or focus trap.
States
Cancel returns focus to the System close control. Confirm submits the operation; the displayed result follows the relevant service outcome.
Specimen
Real Elm interface. Simulated desktop. Client window interiors are fixtures. Load the desktop only when you want to explore this component.
Behavior
A native application can also own a modal window family. That relationship controls its eligible recipient and is separate from the shell’s inline System confirmation.
Accessibility
System confirmation stays in the existing surface, without a modal scrim or focus trap. Cancel precedes Confirm in keyboard order and returns focus to the System close control. Confirm submits the named operation; its subsequent status is announced by the owning surface. Native modal-family recipient rules are a separate client-window relationship.
Content
Name the operation the user is confirming, including network disable, restart, shutdown or logout. Keep Cancel and Confirm distinct. A submitted request is not a completed operation; show the service’s actual result.
Evidence
Captures show the running interface; they are not simulated fixtures.
View SystemMenu source on GitHub (external reference).