-
-
Notifications
You must be signed in to change notification settings - Fork 956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collision detection for Selector dropdowns #64
Comments
absolutely agree, that last dropdown its dfficult to scroll webpage and read menu would be helpful if we set fixed height and overflow: auto Novel.Notion-style.WYSIWYG.editor.with.AI-powered.autocompletions.-.Google.Chrome.2023-06-29.22-24-42.mp4can I work on this? |
is that repo is still active? |
@abhijain1705 don't think a fixed height is the solution here, since you wouldn't know what position the bubble menu is initiated in the DOM and it might still collide with the screen boundaries
Which repo are you referring to? |
then what can be best the solution here? |
Converting the selector menu into a Radix popover primitive should fix this – though it might collide with some of the native Tiptap event listeners somehow |
it's like redeveloping the menu using Radix popover |
Exactly! |
can I contribute to this? |
hey @steven-tey you might busy previously |
@abhijain1705 yes, of course! :) |
thanks |
Currently, the Color and Node Selectors is unable to detect when it's near the bottom of the screen and has to be opened the other way round:
Using something like a Radix Popover could fix this:
CleanShot.2023-06-29.at.08.25.00.mp4
We'll also want to make sure to limit the height of the dropdown and add
overflow-scroll
depending on the screen height.The text was updated successfully, but these errors were encountered: