Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

fix(ngAnimate): ensure invalid merged animations are cleared from the element #11927

Closed
wants to merge 3 commits into from

Conversation

petebacondarwin
Copy link
Contributor

@matsko can you just check that this fix makes sense?

matsko and others added 3 commits May 22, 2015 12:45
…class is added/removed when removed/added

This patch ensures that if the same CSS class is added/removed within a
follow-up digest then the previous class-based animation is cancelled
beforehand.

Closes angular#11717
…class is added/removed when removed/added

This patch ensures that if the same CSS class is added/removed within a
follow-up digest then the previous class-based animation is cancelled
beforehand.

Closes angular#11717
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

@matsko
Copy link
Contributor

matsko commented May 26, 2015

Landed as db246eb

@matsko matsko closed this May 26, 2015
@petebacondarwin petebacondarwin deleted the pr-11755 branch November 24, 2016 09:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants