Skip to content
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

Merged
merged 1 commit into from
Jul 18, 2019

Conversation

crisbeto
Copy link
Member

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.

@crisbeto crisbeto requested a review from jelbourn as a code owner June 26, 2018 20:38
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 26, 2018
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jun 26, 2018
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jun 26, 2018
crisbeto added a commit to crisbeto/material2 that referenced this pull request Jul 25, 2018
…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.
jelbourn pushed a commit that referenced this pull request Aug 1, 2018
…erver (#12378)

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 #11940.
jelbourn pushed a commit that referenced this pull request Aug 7, 2018
…erver (#12378)

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 #11940.
jelbourn pushed a commit that referenced this pull request Aug 7, 2018
…erver (#12378)

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 #11940.
@rharter
Copy link

rharter commented Aug 13, 2018

I'd love to see some movement on this as it's currently blocking me.

@rossanmol
Copy link

Hey, are there any updates on this PR? This PR is crucial for my project :)

@crisbeto crisbeto force-pushed the 11817/overlay-container-cleanup branch from bb4a1ff to 5c2081c Compare January 4, 2019 16:05
@crisbeto crisbeto force-pushed the 11817/overlay-container-cleanup branch from 5c2081c to cc4470b Compare February 18, 2019 19:09
@crisbeto crisbeto force-pushed the 11817/overlay-container-cleanup branch from cc4470b to ee18407 Compare March 22, 2019 17:30
…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.
@crisbeto crisbeto force-pushed the 11817/overlay-container-cleanup branch from ee18407 to 2d1a48f Compare March 22, 2019 22:02
@jelbourn
Copy link
Member

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

@jelbourn jelbourn added P2 The issue is important to a large percentage of users, with a workaround presubmit failures This PR has failures in Google's internal presubmit process and cannot be immediately merged labels Mar 26, 2019
@mmalerba mmalerba added aaa and removed aaa labels Apr 25, 2019
@angular angular deleted a comment from bastienlemaitre Jul 18, 2019
@jelbourn jelbourn merged commit 036729d into angular:master Jul 18, 2019
andrewseguin pushed a commit that referenced this pull request Jul 29, 2019
…rver (#11940)

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.
@mastermsd
Copy link

#15579

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P2 The issue is important to a large percentage of users, with a workaround presubmit failures This PR has failures in Google's internal presubmit process and cannot be immediately merged target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants