Act on Press
Act-on-press vs act-on-release: core arguments
- Act-on-press is praised for feeling “snappier,” matching physical keyboards, and reducing errors from “ballistic taps” and focus drift between down/up.
- Many commenters counter that act-on-release is a long-standing convention for mouse-driven GUIs, and breaking it often feels wrong or surprising.
- Some note that any benefit is on the order of tens of milliseconds and often imperceptible for non-time-critical tasks.
Games vs desktop/mobile UI
- Games nearly always act on press for controls where reaction time matters; release or hold is used for charge mechanics and special moves.
- For game inventories/hotbars, act-on-release plus drag is common: click to use, drag to assign or move. This pattern conflicts with pure act-on-press.
- Several argue that the VR/on-screen keyboard is a special case where matching hardware keyboards (act-on-press) is obviously correct.
Error prevention, safety, and undo
- One camp relies heavily on “press → slide away → release” as a last-moment cancel, especially for destructive or irreversible actions.
- Others argue this is a brittle escape hatch; better patterns are confirmation screens, non-destructive defaults, and especially robust undo.
- Safety‑critical domains are cited as cases where mid-click cancellation is important; timers or abort windows are suggested but seen as complex.
Accessibility and diverse users
- Accessibility guidelines are mentioned: acting on mousedown can be considered problematic unless there is clear abort/undo.
- There’s disagreement whether press or release is better for people with shaky hands; act-on-press reduces follow‑through requirements, but act-on-release allows cancellation by moving off-target.
Touchscreens, gestures, and dragging
- Touch UIs complicate act-on-press: scrolling, long-press menus, drag-and-drop, and “hard press” all require waiting to disambiguate intent.
- Fat‑finger errors and small targets make the ability to drag off to cancel especially valuable.
- Many suggest: if an element is draggable, don’t also make it an instant-acting button.
Conventions, muscle memory, and experiments
- Decades of using act-on-release for mouse actions have trained users; changing this can cause frustration even if technically “faster.”
- A few report experimenting with scripts that convert clicks to mousedown-triggered actions on the web and finding the experience noticeably snappier, with few missed cancellations.
- Others say any mixed environment (some press, some release) is worse than either rule applied consistently.