Briefly crossing multiple targets should not trigger hover content one by one
Aliases: pass-through filtering · hover false trigger · pointer trajectory
What it is
When crossing toolbars, lists, or menus, a pointer briefly passes several targets. Pass-through filtering keeps those unintentional crossings from opening previews, submenus, or bubbles one by one. Dwell, speed, direction, and entry path become evidence that distinguishes passing from wanting to inspect or act.
Why it happens
If every target triggers immediately on entry, a continuous trajectory produces a cascade of overlapping state changes. Delay timers, minimum dwell, trajectory prediction, and mutually exclusive cancellation suppress it. Good filtering preserves fast response at the final target without letting intermediate targets seize attention or block movement.
Studying it
Use tasks that cross dense targets, select a distant item, and explore information. Record intermediate triggers, final-target wait, path backtracking, occlusion, and perceived disruption. Compare timers, speed thresholds, and path tolerance, checking that brief but intentional hovers are not over-filtered.
Where it stops holding
Excess filtering makes an interface feel unresponsive, especially for short but deliberate stops. Not all crossings are accidental: preview browsing, scanning, and expert shortcuts may rely on rapid feedback. Tune by content cost and task mode instead of classifying every short dwell as noise.
Applying it
- Require minimum dwell and cancel uncompleted triggers on exit.
- Smoothly switch mutually exclusive hover content instead of queuing several overlays.
- Demand stronger evidence for disruptive content while retaining faster feedback for lightweight frequent previews.
Related
- Same group: C1.20.1 Hover delay requires a concrete value balancing responsiveness and false triggers · C1.20.2 Hover-open menus and hover tooltips need independent delay thresholds · 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: C1.22 Drag thresholds and intent classification · E1 Interface elements and controls
- Search terms:
pass-through·hover filtering·pointer trajectory
Cards in the same group
- C1.20.1Hover delay requires a concrete value balancing responsiveness and false triggers
- C1.20.2Hover-open menus and hover tooltips need independent delay thresholds
- 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