Skip to content

test(material/menu): referring to wrong overlay element #23186

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

Merged
merged 1 commit into from
Jul 19, 2021

Conversation

crisbeto
Copy link
Member

Attempts to fix the recent flakiness in menu tests. It seems like we were destroying and recreating an overlay container at one point, but we were referring to the element of the previous.

Attempts to fix the recent flakiness in menu tests. It seems like we were destroying and recreating an overlay container at one point, but we were referring to the element of the previous.
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 16, 2021
@crisbeto crisbeto marked this pull request as ready for review July 16, 2021 21:27
@crisbeto crisbeto requested a review from amysorto July 16, 2021 21:27
@crisbeto crisbeto added merge safe P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release labels Jul 16, 2021
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jul 17, 2021
@amysorto amysorto merged commit 3ae6124 into angular:master Jul 19, 2021
amysorto pushed a commit that referenced this pull request Jul 19, 2021
Attempts to fix the recent flakiness in menu tests. It seems like we were destroying and recreating an overlay container at one point, but we were referring to the element of the previous.

(cherry picked from commit 3ae6124)
@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 Aug 19, 2021
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants