-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Open menu should support background scrolling #6927
Comments
@mmalerba Is this intended behavior? |
This used to be the intended behavior (the backdrop blocking scrolling), but now they should reposition |
This only really happens if the scrollable element is the sidenav container, not the body. @jelbourn it is a little tricky to solve, because we'd have to disable pointer events on the backdrop which breaks the clicking outside to close an overlay. It can be resolved by disabling pointer events and using a click handler on the document to determine whether the user clicked outside, but that can be problematic too because the user could stop the event from propagating all the way up. |
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
Fixes a long-standing where the backdrop doesn't allow the user to scroll, if the main scrollable container is not the body. Fixes angular#6927.
hi, I'm running into similar issue that Will the fix be landed on v9 ? For me, I really hope it will be fixed in v9. |
Hey, |
Any updates on this? |
Having still the same issue. Any Update? |
Hello folks, We're focusing on material3, improving our theming system and accessibility. I not sure someone on the Angular team will be able to get to this. Angular Material is open source and we welcome contributions from the community. Feel free to get started on this if you are interested. Best regards, Zach |
Bug, feature request, or proposal:
Bug? Reading the source, when having a menu open, I believe the background should be able to be scrolled using the mouse. The background can be scrolled with the arrow keys.
What is the expected behavior?
The background can scroll.
What is the current behavior?
The background cannot scroll.
What are the steps to reproduce?
What is the use-case or motivation for changing an existing behavior?
A dialog box should block background scrolling, but the menu should not.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Current
Is there anything else we should know?
It is blocked by
pointer-events: auto
: https://github.com/angular/material2/blob/4d82f833c7e4a22814b8e225f05ef4ba01a86ad6/src/cdk/overlay/_overlay.scss#L61.The menu does have the scroll strategy of reposition, which I believe should mean that the background should be able to be scrolled: https://github.com/angular/material2/blob/fe37cb2551929844d5467e1b9bf45032df35981f/src/lib/menu/menu-trigger.ts#L57
The text was updated successfully, but these errors were encountered: