perf(material-experimental/mdc-chips): avoid excessive change detection on transitionend #19039
Conversation
This file contains hidden or 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
…on on transitionend The MDC-based chip has a `transitionend` event on the root that fires very frequently for things like ripples, but the chip only cares about the ones on `width` and `opacity`. These changes run the event outside of Angular and only bring it back inside when necessary.
crisbeto
added
P3
googlebot
added
the
cla: yes
|
Meh, looks like I made a PR for this already and I forgot about it. #18043. |
|
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.
The MDC-based chip has a
transitionendevent on the root that fires very frequently for things like ripples, but the chip only cares about the ones onwidthandopacity. These changes run the event outside of Angular and only bring it back inside when necessary.