-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Animation staggering issue in 1.4.4 #12594
Comments
1+ I've experienced this as well. I've had to use 1.4.3 of angular-animate |
+1 |
@matsko can you take a look? |
This isn't entirely broken. You can still get the stagger to work by adding http://plnkr.co/edit/PSuu2IOG03fv2ifNTTwQ?p=preview This was mentioned in the stagger docs: Unfortunately with 1.4.4 and onwards this is always the case. You must always define the duration value as 0s since we changed the way the ng-EVENT classes are applied. I completely missed making note of this in the CHANGELOG as a breaking change. I will make sure it shows up in the 1.4.5 release notes. |
…erty As of 1.4.4 this property needs to always be in the CSS code Related angular#12594
This PR contains a fix to the docs: #12637 |
…erty As of 1.4.4 this property needs to always be in the CSS code Related angular#12594
Thanks, that helped for the transition animation. And what about the keyframes animation? I tried it with the 'animation-duration: 0s' property, but it didn't help. |
I met the issue like @serjrd too, the 1.4.4 version still has a bug in keyframes when use stagger. And my code like below: when you choose 1.4.3 version, the code works fine. Another thing I have noticed that when you write 'transition-duration: 0' without 's', the stagger not performed like we expected, but in 1.4.3, it works. |
There is a fix in place for 1.4.5 that fixes both: http://plnkr.co/edit/SkKZaH6qQmgX5w6YoGk9?p=preview |
@matsko It works fine, thank you! |
This reverts the previous behaviour of using foreced reflows to deal with preparation classes in favour of a system that uses requestAnimationFrame (RAF). Closes angular#12669 Closes angular#12594 Closes angular#12655 Closes angular#12631 Closes angular#12612
This reverts the previous behaviour of using foreced reflows to deal with preparation classes in favour of a system that uses requestAnimationFrame (RAF). Closes angular#12669 Closes angular#12594 Closes angular#12655 Closes angular#12631 Closes angular#12612 Closes angular#12187
This reverts the previous behaviour of using foreced reflows to deal with preparation classes in favour of a system that uses requestAnimationFrame (RAF). Closes angular#12669 Closes angular#12594 Closes angular#12655 Closes angular#12631 Closes angular#12612 Closes angular#12187
This reverts the previous behaviour of using foreced reflows to deal with preparation classes in favour of a system that uses requestAnimationFrame (RAF). Closes angular#12669 Closes angular#12594 Closes angular#12655 Closes angular#12631 Closes angular#12612 Closes angular#12187
Here's a plunker snippet that illustrates the issue: http://plnkr.co/edit/PSuu2IOG03fv2ifNTTwQ?p=preview
With the version 1.4.4 there's no staggering.
But If you change the included angular version to 1.4.3 - staggering works fine.
This is under Ubuntu / Chrome Version 44.0.2403.125 (64-bit).
The text was updated successfully, but these errors were encountered: