-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Navigation: Don't interfere with pointer events #51378
Conversation
Size Change: -347 B (0%) Total Size: 1.39 MB
ℹ️ View Unchanged
|
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.
I tested this and I was able to replicate the bug on trunk
and confirm it is fixed on this branch.
Nice work. I'd be broadly in favour of merging except that I'm a little confused about the purpose of the code we're removing.
Looks like it was modified by @noisysocks fairly recently. I wonder if he could shed some light on it?
Also @vcanales wrote the original code in #30047 so he might have ideas.
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.
This works great. The code removed seems to me like a relic.
I hated it and am glad to see it gone 😂 |
What?
This CSS was messing with pointer events which made it possible to select a block that was behind the navigation overlay.
Why?
Users shouldn't be able to select blocks that are behind the navigation overlay when it is open.
How?
This code was messing around with the pointer events in the navigation block. Just deleting it seems to restore the behaviour we want and doesn't seem to cause any other issues.
Testing Instructions
Testing Instructions for Keyboard
Follow the steps above and confirm that the block can still be used with a keyboard.
Screenshots or screencast
See #51291