Hover-open menus and hover tooltips need independent delay thresholds
Aliases: menu delay · tooltip · hover threshold
What it is
Hover-opening a menu and revealing an explanatory tooltip are both dwell-triggered, but have different intent, consequences, and timing needs. Context-specific delay sets them separately: menus support continuous navigation, while tooltips should not interrupt scanning or obscure content, so one global wait is inappropriate.
Why it happens
Entering a menu item is often part of a navigation path, and a slow submenu interrupts movement. A tooltip supplies secondary information, and appearing too quickly can cover the next target. Content size, interactivity, exit behaviour, and error cost differ, so timers, grace regions, and cancellation rules should differ too.
Studying it
Evaluate candidate values separately with menu-selection and information-reading tasks, measuring path interruption, accidental opening, tooltip reading, occlusion backtracking, and time. Do not copy an optimum from one context to another; also test continuity while moving into a submenu or tooltip.
Where it stops holding
Independent values do not mean arbitrary values for every control. Components of the same type should remain consistent, and differences need task-based justification. If a tip holds critical instruction, make it persistent and triggerable rather than merely shortening hover delay.
Applying it
- Establish component-level defaults and validation criteria for menus, tooltips, and previews.
- Combine menu delay with path tolerance toward submenus rather than only reducing the timer.
- Put important guidance in clickable or focusable UI; use hover as a supplement.
Related
- Same group: C1.20.1 Hover delay requires a concrete value balancing responsiveness and false triggers · C1.20.3 Briefly crossing multiple targets should not trigger hover content one by one · C1.20.4 An exit grace period prevents hover content from disappearing immediately from tremor · C1.20.5 Hover-induced layout changes can occlude the next interaction path
- Nearby: E1 Interface elements and controls · C1.19 Cursor shapes as state expression
- Search terms:
menu delay·tooltip·hover
Cards in the same group
- C1.20.1Hover delay requires a concrete value balancing responsiveness and false triggers
- C1.20.3Briefly crossing multiple targets should not trigger hover content one by one
- C1.20.4An exit grace period prevents hover content from disappearing immediately from tremor
- C1.20.5Hover-induced layout changes can occlude the next interaction path