Why does ngView add the new element before the previous element when animating?

[Siyfion]

This seems like it's completely the wrong way around to me, if you want to do a simple fadeOut -> fadeIn animation, you can't get it to look good because the new view pushes the old view down instantly.

I guess you could change the animation to a keyframed anim and set display: none until it starts, but it's a bit overkill..?

[petebacondarwin]

If you are doing fade animations then you would need the new element to be hidden initially either way, no?

Even if it was add after the old element, without display: none, it would appear below the old one.

[matsko]

It does this because the previous scope+element gets cleaned up (scope destroyed + leave animation), and then by the time the enter animation occurs it uses the transclusion anchor as the previous sibling. This is set like this because if there are no animations then the leave element is gone by the time the enter insertion comes up and it has no element to insert after (aside from the transclusion anchor). This should be changed though.

[matsko]

Waiting for the PR to be merged.