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

fix($animateCss): ensure that custom durations do not confuse the gcs cache #11852

Closed
wants to merge 1 commit into from

Conversation

matsko
Copy link
Contributor

@matsko matsko commented May 11, 2015

Closes #11723

@@ -742,6 +742,9 @@ var $AnimateCssProvider = ['$animateProvider', function($animateProvider) {
applyAnimationClasses(element, options);
applyAnimationStyles(element, options);

// we increment the counter so that if the same element is animated
// then the existing cache will not apply to it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand the context of this comment. Where is the counter that is being incremented?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry that is dead code from a previous fix I had in mind.

@matsko matsko force-pushed the animate_css_cache_break branch from 34c4426 to 8576671 Compare May 22, 2015 21:02
@matsko matsko closed this in e0e1b52 May 23, 2015
netman92 pushed a commit to netman92/angular.js that referenced this pull request Aug 8, 2015
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.

Weird behavior of $animateCss with ng-if and quick toggling of elements in 1.4.0rc1
4 participants