UI & interactionHold to confirm, four ways
A safe button for actions that cost something: it acts only after being held.
One accessible context-menu core (roles, arrow keys, type-ahead, letter keys, Esc, focus kept and given back, stays on screen, right-click, long-press and…
Measured 7 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 156, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: Measured opening and closing a menu every 0.8 s across the six skins (each open builds, lays out and focuses the menu inside the timed frame; the animations run on the compositor). Idle, the menus cost nothing. Phones: tiers are being measured next.
| Machine | GPU ms | CPU ms | CPU p95 |
|---|---|---|---|
| unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring tool | not timed | <0.01 | 0.01 |
| apple · Apple A19 Proin a browser tab · 16 November 2026 | not timed | <0.01 | 0.02 |
| Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026 | not timed | <0.01 | 0.01 |
Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.
From HaTac. Fully custom code.
W3C WAI-ARIA Authoring Practices: Menu pattern: The roles, focus movement and keys follow the pattern (written here from scratch).
Pie menus (Callahan, Hopkins, Weiser and Shneiderman, 1988): The radial disc picks by the pointer’s direction from the centre, as in their study of pie menus.