ngAnimate: Wrong classes attached to element with animations

[mik01aj]

I got an element with ng-class="{shown: !!some.condition}", initially shown, and I noticed that it has weird classes attached. I set up a breakpoint to watch changes of this element, and here's how the class list changed:

1. thumbnails ng-isolate-scope ng-scope shown
2. thumbnails ng-isolate-scope ng-scope shown shown-add-active (attached stackrace is from here)
3. then some time passes... ($timeout)
4. thumbnails ng-isolate-scope ng-scope shown shown-add-active ng-animate
5. thumbnails ng-isolate-scope ng-scope shown shown-add-active ng-animate shown-remove
6. thumbnails ng-isolate-scope ng-scope shown shown-add-active ng-animate shown-remove shown-remove-active
7. thumbnails ng-isolate-scope ng-scope shown shown-add-active ng-animate shown-remove-active
8. thumbnails ng-isolate-scope ng-scope shown shown-add-active ng-animate
9. thumbnails ng-isolate-scope ng-scope shown shown-add-active
10. thumbnails ng-isolate-scope ng-scope shown-add-active
11. ...and it stays stuck in this position.

One interesting thing I noted was also that the last change (10) was done by jqLite, not jQuery (which we use in our project).

Here's also a stacktrace from step 2:

I use the newest angular (d434eabec3 from master).

[matsko]

I fixed an issue relative to this yesterday. Could you perhaps try using the latest snapshot and see if this problem presists? http://code.angularjs.org/snapshot/

[mgol]

@matsko As @mik01aj stated, we're using Angular from commit d434eab which is the newest commit on the master branch.

[olostan]

I had issue that looked like that.

The reason what in not quite strictly ordered CSS. Check weight of your css's selectors - keep in mind that "xxx-add" should have less weight of 'xxx-add-active'.

I don't know is it a problem or it is supposed to be in this way, but it least if worked for me.

[matsko]

I noticed this same bug yesterday in app that I was writing. I'm checking the fix right now and I'll have a new branch that you guys can test it out on.

[matsko]

Please try the code in this commit: matsko@f018810

[mik01aj]

@matsko: Yes, this fixed the bug, thank you! However we are still experiencing other strange behaviours with ngAnimate classes staying forever on an element. But I think it's a topic for another issue.

[matsko]

@mik01aj can you provide some more info is possible?