Diagonal movement in cascading menus is a typical constrained channel
Aliases: menu steering · menu triangle
What it is
In a cascading menu, moving diagonally from a parent item to a child menu often requires the pointer to remain in an implicit channel between them. A small deviation crosses a neighbouring parent item, closing or switching the submenu. This is a steering-law constrained path, not simply a clicking problem.
Why it happens
The submenu is normally sustained by hover. During diagonal travel, its allowed region is shaped by the parent boundary, adjacent items, and submenu placement. Longer distance and narrower channel require slower, finer correction. Short menu items or distant submenus reduce angular tolerance and make accidental parent entry more costly.
Studying it
Ask participants to complete cascade tasks with varied direction, gap, item height, and open delay. Log trajectories, wrong opens, closures, retries, and child-acquisition time. Trajectory overlays reveal the actual safe region better than asking whether it “feels difficult.” Test mouse, trackpad, and touch alternatives separately because their hover conditions differ.
Where it stops holding
When a menu is click-pinned, overlaps the parent, or changes to a new level after a click, diagonal hover steering is not the main constraint. Touch lacks dependable hover, so copying desktop cascades introduces different errors and discoverability issues. A menu triangle alone cannot fix naming, hierarchy depth, or delay problems.
Applying it
- Shorten the horizontal gap, increase parent-item height, or overlap the child's entrance vertically to widen the diagonal safe region.
- Where hover is required, tolerate a brief departure before closing or infer a trajectory heading toward the submenu.
- Inspect task recordings: frequent pauses followed by cautious sideways motion point to a channel bottleneck rather than a label problem.