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

fix($animateCss): properly handle cancellation timeouts for follow-up animations #12490

Closed
wants to merge 1 commit into from

Conversation

matsko
Copy link
Contributor

@matsko matsko commented Aug 3, 2015

Prior to this fix if $animateCss was called multiple on the same
element with new animation data then the preceeding fallback timout
would cause the animation to cancel midway. This fix ensures that
$animateCss can be triggered multiple times and only when the final
timeout has passed then all animations will be closed.

Closes #12359

@matsko matsko force-pushed the pr_12359 branch 2 times, most recently from 00b8f43 to 09b286e Compare August 3, 2015 18:59
@matsko matsko added this to the 1.4.4 milestone Aug 3, 2015
@matsko matsko assigned matsko and IgorMinar and unassigned matsko Aug 3, 2015
@Narretz Narretz modified the milestones: 1.4.4, 1.4.5 Aug 14, 2015
… animations

Prior to this fix if `$animateCss` was called multiple on the same
element with new animation data then the preceeding fallback timout
would cause the animation to cancel midway. This fix ensures that
`$animateCss` can be triggered multiple times and only when the final
timeout has passed then all animations will be closed.

Closes angular#12359
@matsko matsko closed this in d881673 Aug 18, 2015
@matsko matsko deleted the pr_12359 branch August 18, 2015 20:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng-animate skips animation "under pressure"
4 participants