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.
Please try to remove an element to reproduce the problem.
After @matsko:
"It looks like both ngInclude and ngRepeat are competing for who gets to animate the leave operation. Normally this isn't a problem, but when a destructive DOM operation happens which removes the element before the next animation takes place, then this leads up to the next animation having no element to perform the animation on."
The text was updated successfully, but these errors were encountered:
I am opening this ticket as @matsko suggested. Continuing from #4871.
Here is the plunkr with an example of the issue:
http://plnkr.co/edit/iVrtMJg92Iip9arTLXpx?p=preview
Please try to remove an element to reproduce the problem.
After @matsko:
"It looks like both ngInclude and ngRepeat are competing for who gets to animate the leave operation. Normally this isn't a problem, but when a destructive DOM operation happens which removes the element before the next animation takes place, then this leads up to the next animation having no element to perform the animation on."
The text was updated successfully, but these errors were encountered: