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.
Do you want to request a feature or report a bug?
feature
What is the current behavior?
when using ngAnimate's move feature in ngRepeat directives, the ng-move-* classes are only applied to the element once it was moved.
What is the expected behavior?
It would be nice to have a better control over the animation of elements before they move, for example by having: ng-move-leave(-active)? & ng-move-enter(-active)? classes.
Not sure if the ng-move-enter animation should wait for the ng-move-leave animation to finish or if both animations should be simultaneous. I guess a css's transition-delay may be the answer to this.
What is the motivation / use case for changing the behavior?
Allow fading out element when they are being moved, instead of them suddenly disappearing from one place, and appearing nicely in another.
Which versions of Angular, and which browser / OS are affected by this issue?
Angular 1.5.8
Chrome 52