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
The text was updated successfully, but these errors were encountered:
+1
I would like this feature as well. Moved items should transition smoothly and not jump into their new position. Animating a position change would be difficult. Fading a moved item out from it's previous position and fading it up in its next position sounds plausible.
This feature was the motivation behind issue #15068. Here is a plunker with the revised ngRepeat code.
Perhaps when ngRepeat performs actions on the collection, all items that need to enter or leave should wait until all moved items have finished animating?
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, theng-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 theng-move-leave
animation to finish or if both animations should be simultaneous. I guess a css'stransition-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
The text was updated successfully, but these errors were encountered: