Avoid accidentally closing (sub-)menu too early
mtlynch opened this issue · comments
One of the things I noticed in a lot of the videos for https://github.com/tiny-pilot/tinypilot-pro/pull/1169 was that there are a lot of instances where Jason was navigating the menu and the menu closed too fast because he moved his cursor just off the menu.
We should explore increasing the timeout so that the menu stays visible for an extra 100-200ms after the cursor leaves the menu area.
There is a closely related usability issue, which likely might (or rather: should) be addressed by the same solution (i.e., the proposed delay).
When hovering over a menu item to open a sub-menu, and then moving the cursor diagonally into the sub-menu, it might occur that the sub-menu closes due to the trajectory of the cursor.
If the cursor follows the red trajectory, it briefly leaves the “Networking” menu item, which causes the sub-menu to close immediately. Only if you follow the green trajectory, the sub-menu stays open.
(Sorry, by the way, for psychoanalyzing you here @jdeanwallace, but I noticed in your screen recordings that you do a very good job to carefully follow that green trajectory 🤣)
Screen.Recording.2024-01-23.at.19.03.38.mov
(The timing in the video is a bit exaggerated.)
For reference, macOS also uses the delay technique in their native UIs: