Add safe triangle behavior for nested menus#420
Merged
Conversation
genusistimelord
approved these changes
Apr 27, 2026
genusistimelord
left a comment
genusistimelord
left a comment
Collaborator
There was a problem hiding this comment.
thank you this looks good.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I inroduced the safe triangle behavior for menu interactions. It tracks the last cursor position over a parent menu item, builds a triangular safe area toward the opened submenu, and keeps the submenu open while the cursor moves through that area. This prevents nested menus from closing prematurely when users move the cursor from a parent item into its child menu.
Demonstrated by
Before:
Screen.Recording.2026-04-26.at.22.24.19.mov
Now:
Screen.Recording.2026-04-26.at.22.26.58.mov