-
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): clear duplicate overlay container coming in from the server #11940
fix(overlay): clear duplicate overlay container coming in from the server #11940
Conversation
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
…erver Fixes the case where the user might get multiple live announcer elements, if they're coming in from a server-side-rendered page. Along the same lines as angular#11940.
I'd love to see some movement on this as it's currently blocking me. |
Hey, are there any updates on this PR? This PR is crucial for my project :) |
bb4a1ff
to
5c2081c
Compare
5c2081c
to
cc4470b
Compare
cc4470b
to
ee18407
Compare
…rver When coming from a server-side-rendered page, we may end up in a situation where there are multiple overlay containers on the page with stale overlays in them. These changes clear all old overlay containers before creating a new one. Relates to angular#11817.
ee18407
to
2d1a48f
Compare
Looks like there were a handful of unit test failures inside Google on this change. I'll see if we're able to debug them |
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. |
When coming from a server-side-rendered page, we may end up in a situation where there are multiple overlay containers on the page with stale overlays in them. These changes clear all old overlay containers before creating a new one.
Relates to #11817.