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 has been archived by the owner on Apr 12, 2024. It is now read-only.
When items in ng-repeat are tracked by index and animation is used on ng-leave the item is removed and then a wrong item is duplicated and the animation is applied on that duplication.
If one is using images and wants images with same sources to be included in the ng-repeat directive then track by $index is necessary.
Here's another thought on the matter as consequence to the behavior.
Imagine there is watcher in directive that keeps track of the ng-repeated items and actualities a css width removing item and animation may cause wrong behavior in that case.
The text was updated successfully, but these errors were encountered:
When items in
ng-repeat
are tracked by index and animation is used onng-leave
the item is removed and then a wrong item is duplicated and the animation is applied on that duplication.Here's a fresh example
This issue seems to be relatively old: stackoverflow
If one is using images and wants images with same sources to be included in the ng-repeat directive then
track by $index
is necessary.Here's another thought on the matter as consequence to the behavior.
Imagine there is watcher in directive that keeps track of the ng-repeated items and actualities a css
width
removing item and animation may cause wrong behavior in that case.The text was updated successfully, but these errors were encountered: