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

fix($animateCss): ensure that detection cache is flushed after animation is closed #11805

Closed
wants to merge 1 commit into from

Conversation

matsko
Copy link
Contributor

@matsko matsko commented May 5, 2015

Closes #11723

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

// we need to clear the cache since the post-quiet state may add and remove CSS
// classes which contain follow-up animation data which will be cached.
$$rAF(function() {
Copy link
Member

Choose a reason for hiding this comment

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

It doesn't make any difference, but it could be $$rAF(flushGCSCache).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed up.

@petebacondarwin petebacondarwin added this to the 1.4.0-rc.2 milestone May 5, 2015
…ion is closed

In the post-quiet animation detection phase of $animateCss there is a
call to getComputedStyle which is cached, however, the cache is not
cleared until the next animation is run. This causes a caching issue
since the next animation's cache data may be read and provided
incorrectly. This patch clears the cache after each animation has
closed itself.

Closes angular#11723
@matsko matsko changed the title fix($animateCss): ensure that detection cache is flushed after animation is closed fix($animateCss): ensure that custom durations do not confuse the gcs cache May 11, 2015
@matsko matsko changed the title fix($animateCss): ensure that custom durations do not confuse the gcs cache fix($animateCss): ensure that detection cache is flushed after animation is closed May 11, 2015
@matsko
Copy link
Contributor Author

matsko commented May 11, 2015

Closed in favour of: #11852

@matsko matsko closed this May 11, 2015
@matsko matsko deleted the fix_pr_11723 branch May 11, 2015 20:32
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