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(material/core): noop animations not applying to selector lists #24904

Merged
merged 1 commit into from
May 11, 2022

Conversation

crisbeto
Copy link
Member

The way the private-animation-noop mixin was written meant that if it was included in a list of selectors, it would only be applied to the first selector in the list. This caused some animations in the MDC button not to be disabled.

These changes simplify the mixin, because the old approach was only relevant for on case in the progress spinner that we can write out manually instead.

The way the `private-animation-noop` mixin was written meant that if it was included in a list of selectors, it would only be applied to the first selector in the list. This caused some animations in the MDC button not to be disabled.

These changes simplify the mixin, because the old approach was only relevant for on case in the progress spinner that we can write out manually instead.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent G This is is related to a Google internal issue target: patch This PR is targeted for the next patch release labels May 11, 2022
@andrewseguin andrewseguin added the action: merge The PR is ready for merge by the caretaker label May 11, 2022
@crisbeto crisbeto added target: rc This PR is targeted for the next release-candidate and removed target: patch This PR is targeted for the next patch release labels May 11, 2022
@crisbeto crisbeto merged commit cc5326c into angular:main May 11, 2022
crisbeto added a commit that referenced this pull request May 11, 2022
…24904)

The way the `private-animation-noop` mixin was written meant that if it was included in a list of selectors, it would only be applied to the first selector in the list. This caused some animations in the MDC button not to be disabled.

These changes simplify the mixin, because the old approach was only relevant for on case in the progress spinner that we can write out manually instead.

(cherry picked from commit cc5326c)
@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 Jun 11, 2022
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 G This is is related to a Google internal issue P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants