fix(menu): changed after checked error when toggling quickly between triggers for same submenu #12209
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…triggers for same submenu Fixes `mat-menu` throwing a "changed after checked" error when moving quickly between triggers for the same sub-menu. Fixes angular#12194.
googlebot
added
the
cla: yes
jelbourn
added
pr: lgtm
action: merge
|
Caretaker note: may cause test issues due to async behavior change |
josephperrott
pushed a commit
that referenced
this pull request
Jul 18, 2018
…triggers for same submenu (#12209)
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes
mat-menuthrowing a "changed after checked" error when moving quickly between triggers for the same sub-menu.Fixes #12194.
Note: I wasn't able to get the same error to be thrown during unit tests, potentially because change detection and animations are being triggered manually during tests.