-
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
fix(overlay): flexible overlay with push not handling scroll offset and position locking #12624
fix(overlay): flexible overlay with push not handling scroll offset and position locking #12624
Conversation
Caretaker note: this change has messed up menus in Firebase twice now. Do not merge without validating that the issue is resolved with a Firebase team member. |
Hi @crisbeto! This PR has merge conflicts due to recent upstream merges. |
afb4639
to
66e6e37
Compare
@crisbeto figured out that's going on with the g3 failures. You added |
…nd position locking * Fixes the position of flexible overlays with pushing enabled being thrown off once the user starts scrolling. * Fixes flexible overlays with pushing not handling locked positioning. With these changes locked overlays will only be pushed when they're opened, whereas non-locked overlays will stay in the viewport, even when the user scrolls down. * Fixes a potential issue due to a couple of variables being initialized together where one is set to zero and the other one is undefined. Fixes angular#11365.
66e6e37
to
f5408a7
Compare
@mmalerba I'm not sure why somebody would have tests for this case, but it makes sense ¯\_(ツ)_/¯. I've reworked it so it treats repositioning after a page resize as a new render and it picks a new optimal position. |
Good work @crisbeto! Wondering when can this be merged? Anxiously waiting for a fix to this one |
Hi @crisbeto ! Good work, I am wondering if this PR was merged because I just saw that there is a new material version (6.4.7) and I can't find these changes applied. Thank you :) |
It's in the 7.0 beta. |
Hii @crisbeto how are you!? Is it possible for any chance that this fixed can be push in version 6?? Because It's a blocker for us, it's breaking the functionality in our site. |
@crisbeto this issue breaks and existing functionality on our Production website. There is any chance we can push this code to a future 6.X.X release? If not, what's the blocker? There is any known workaround? Thanks in advance. |
On Cordova, the menus sometimes don't appear to open at all because they're positioned off screen. For those that end up here from google, it looks like this has been included in 7.0.0-beta-0. |
…ng to be merge into 6.4.X. * Fixes the position of flexible overlays with pushing enabled being thrown off once the user starts scrolling. * Fixes flexible overlays with pushing not handling locked positioning. With these changes locked overlays will only be pushed when they're opened, whereas non-locked overlays will stay in the viewport, even when the user scrolls down. * Fixes a potential issue due to a couple of variables being initialized together where one is set to zero and the other one is undefined. Fixes angular#11365.
…e merge into 6.4.X. * Fixes the position of flexible overlays with pushing enabled being thrown off once the user starts scrolling. * Fixes flexible overlays with pushing not handling locked positioning. With these changes locked overlays will only be pushed when they're opened, whereas non-locked overlays will stay in the viewport, even when the user scrolls down. * Fixes a potential issue due to a couple of variables being initialized together where one is set to zero and the other one is undefined. Fixes #11365.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This is a resubmit of #11628.
Fixes #11365.