-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[CL-104] fix overlay + virtual scroll view recycling bug #6179
Conversation
New Issues
Fixed Issues
|
@Hinton: I talked with @jtouchstonebw and we aligned on the behavior of blocking scrolling when the menu is open. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, tested and seems to behave as expected. It's a bit odd that you can't see the position in the scrollbar while a menu is open, but that's a side effect of how browsers works.
We can't combine overlay scroll blocking with virtual scroll--they don't work well together in Chrome & Safari. 😭 menu_issue.mp4Instead, we will disable view recycling for now as we investigate a more long term solution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, LGTM!
Type of change
Objective
This PR disables view recycling in
vault-items
. This prevents a bug where the overlay menu would reattach onto new elements after scrolling in a virtual scroll viewport.While testing this change on the
vault-items
story in Storybook, a bug was also found with thefallback-src
directive. If the fallback itself is missing, the directive will request the resource in an infinite loop. This was fixed by only trying to set the fallback image once.Code changes
Screenshots
Before you submit