-
Notifications
You must be signed in to change notification settings - Fork 27.5k
Animations don't fire #4679
Comments
I actually came upon this last Friday - this will get it to work: http://jsfiddle.net/5zJQx/1/ I think something is up with the *-add and *-remove not being added in the right order - the point of them is to allow you to programmatically set the transitions & thus have a more controlled way of triggering the CSS animations, but this is currently not working the way it was intended. This does not work properly in Chrome or Firefox that I've tested (newest for each), so I suspect it's a |
@wesleycho - your example doesn't use ngAnimate at all, just ordinary CSS transitions. Consider this simplified example: http://jsfiddle.net/nbPvW/1/ (note ngAnimate removed from dependencies). |
Ah, sorry, I didn't look closely enough - just assumed he was already using the animations since he had whipped up a fiddle. I came across the same problem myself though, but haven't attempted to reproduce it yet. |
Landed as d434eab |
@matsko Thanks :) |
Look at this simple jsFiddle: http://jsfiddle.net/5zJQx/; animations transitioning between states don't fire.
Now, it's possible that I've used it incorrectly but I looked at it a couple of times and it seemed OK (transitions are set on the
*-add
and*-remove
classes) andngAnimate
documentation under: http://docs.angularjs.org/api/ngAnimate currently says very little about animations not involving entering/leaving elements...The text was updated successfully, but these errors were encountered: