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

fix(ngAnimate): ensure that cancelled class-based animations are properly cleaned up #11899

Closed
wants to merge 1 commit into from

Conversation

matsko
Copy link
Contributor

@matsko matsko commented May 18, 2015

Prior to this fix if the same CSS class was added and removed quickly
then the element being animated would be left with a stale cache of the
cancelled out animation. This would then result in follow-up animations
being added to the previous animation which would then never run. A
stale cache was to blame for that. This patch takes care of this issue.

Closes #11652

@gkalpak
Copy link
Member

gkalpak commented May 19, 2015

LGTM 😉

@Narretz
Copy link
Contributor

Narretz commented May 19, 2015

LGTM2!

…erly cleaned up

Prior to this fix if the same CSS class was added and removed quickly
then the element being animated would be left with a stale cache of the
cancelled out animation. This would then result in follow-up animations
being added to the previous animation which would then never run. A
stale cache was to blame for that. This patch takes care of this issue.

Closes angular#11652
@matsko
Copy link
Contributor Author

matsko commented May 20, 2015

Merged as 718ff84

@matsko matsko closed this May 20, 2015
@matsko matsko deleted the fix_pr_11652 branch May 20, 2015 03:55
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.

Problem with <input type="email" /> and form validation
4 participants