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

Animate fixes #5015

Closed
wants to merge 5 commits into from
Closed

Animate fixes #5015

wants to merge 5 commits into from

Conversation

matsko
Copy link
Contributor

@matsko matsko commented Nov 19, 2013

Closes #4892
Closes #4902
Closes #4944
Closes #4949
Closes #4952
Closes #4960
Closes #4265
Closes #5014
Closes #5018

@toota151
Copy link

5150

@matsko
Copy link
Contributor Author

matsko commented Nov 21, 2013

@toota151 not sure what you mean by "5150".

…essary

When $compile interpolates a CSS class attribute expression it will
do so by comparing the CSS class value already present on the element.
This may lead to unexpected results when dealing with ngClass values being
added and removed therefore it is best that both compile and ngClass delegate
addClass/removeClass operations to the same block of code.
…dom operation occurs

Transitions are blocked when the base CSS class is added at the start of the animation. This
causes an issue if the followup CSS class contains animatable-styles. Now, once the animation
active state is triggered (when the animation CSS dom operation occurs) the animation itself
will always trigger an animate without a quick jump.

Closes angular#5014
Closes angular#4265
Keyframe animations trigger on the first CSS class and not the second.
This may cause a slight flicker during a stagger animation since the
animation has already started before the stagger delay is considered.
This fix ensures that the animation is blocked until the active animation
starts which allows for staggering animations to take over properly.

Closes angular#5018
@matsko
Copy link
Contributor Author

matsko commented Nov 22, 2013

MERGED

@matsko matsko closed this Nov 22, 2013
@matsko matsko deleted the animate_fixes branch November 22, 2013 01:50
@hswolff
Copy link

hswolff commented Nov 22, 2013

🎆

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.