- Issue created by @finnsky
- First commit to issue fork.
- Status changed to Needs review
about 1 year ago 3:43am 20 November 2023 - 🇷🇺Russia kostyashupenko Omsk
Well, what i'm thinking is that:
1. We should not move popover wrapper when inner menus are collapsing/expanding.
2. We should have scrollbar if content of popover is too highKnowing that say that i provided only patch with minimum efforts. I moved arrow chevron into the control button itself (and removed all JS related to arrow). Because arrow should be anyway always placed centered with control button. ANother reason is that for popover wrapper we need vertical scrollbar. And arrow is placed out of visible area of wrapper (which means by adding overflow: auto arrows becomes hidden).
Please test it / share your thoughts. We can try to solve this issue other way
- Status changed to Needs work
about 1 year ago 6:37pm 20 November 2023 - 🇪🇸Spain ckrina Barcelona
The initial 3 assumptions are OK on a UX perspective:
- Rearrange the flyout if it ends up having any part outside of the screen.
- We should not move popover wrapper when inner menus are collapsing/expanding.
- Have scrollbar if content of popover is too high.
But the the resulting interaction could still be improved because it feels really weird to scroll within a flyout when there is enough vertical space. Your instincts are right though: not moving the thing you're clicking after an interaction. So I think we could do something similar to the bottom user menu and scroll to the bottom side of that submenu? It's a bit of an extreme case but punishing all submenu flyout interactions with a flyout seems a bit extreme. Let's build that and we'll add this into the next round of tests to verify if it's annoying.
- 🇷🇺Russia kostyashupenko Omsk
@ckrina not really clear what you meant, can you rephrase maybe or provide some better explanation / examples?
I'm uploading video where i'm interacting with flyout menu. Feels pretty intuitive to me
- 🇷🇸Serbia finnsky
We may optionally use Autoupdate feature of floating UI.
https://floating-ui.com/docs/autoUpdate - Merge request !142Recalculate popover position on menu toggle - #3402417 → (Open) created by finnsky
- Status changed to Needs review
12 months ago 5:30pm 29 November 2023 - 🇷🇸Serbia finnsky
Seems autoupdate it is not exactly what we need here. I added more simple solution with CustomEvents.
We recalculate position if in result of submenu trigger popover goes out of screen. - Status changed to Needs work
12 months ago 8:14am 30 November 2023 - 🇷🇺Russia kostyashupenko Omsk
I see two problems. One of these problems i already raised above:
1. When there is not enough space to display a whole menu with sub-menus expanded - my personal feeling is that my cursor should be positioned on the button i just clicked. But with the last patch content is moving when opened so it's pretty uncomfortable when the element you just clicked becomes out of cursor.
2. If there is not enough space to display popover fully - nothing happening, a part of content becomes just out of viewport. Intuitively i'm expecting to have scrollbar.
Merge requests 131 resolves these problems and it is still up-to-date (i just rebased it just in case you want to have a look once again how it's working).
- Status changed to Closed: outdated
8 months ago 6:11pm 4 April 2024