You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
..and the reason why I'm doing all this instead of simply adding ng-class to .animation itself, is because it seems to bug out when I try and use ng-class with the same varible on two different elements(only one transition happens, the other is instantly at the finished state)... it might be a bug in $animation, but I'm not entirely sure
The text was updated successfully, but these errors were encountered:
Yeah... I encoutered more than one strange/buggy behaviour, in cases which worked just fine while testing it with pure css(with :hover).. but it's gonna take a while to extract it from the thing I'm working on.. so yeah, eventually, just not now.
Why I need it..
Look at this structure.
and I'd like to do something like this
..and the reason why I'm doing all this instead of simply adding ng-class to
.animation
itself, is because it seems to bug out when I try and use ng-class with the same varible on two different elements(only one transition happens, the other is instantly at the finished state)... it might be a bug in $animation, but I'm not entirely sureThe text was updated successfully, but these errors were encountered: