Different DOM when using template vs templateUrl with replace true

[kopatsy]

When repeating a directive with replace=true and a templateUrl, all the elements of the repeated directives end up in the last repetition.

The only difference between the two plnkr's below is that the first one is using templateUrl while the second one is using an inlined template. The rendering is however different.

With templateUrl (broken): http://plnkr.co/edit/c7jZSldkkQxzjNRZHcPZ
With template (working): http://plnkr.co/edit/aMm6eReAZ4C5WgrsMddD

[kopatsy]

Unit test reproducing the issue: https://gist.github.com/kopatsy/a9083762cc8cf479b2d6

[neberej]

I have faced similar issues on past. Wrapping ng-repeat element with div fixes it. Though I cant explain why.

[lgalfaso]

there are a few previously reported issues on different variations of this. The main issue is that when replace=true and there is a directive at the top level of the directive that specifies replace=true or transclude=element, then the compilation runs into this issue. It is not a simple problem to solve, but it falls into the small variations that are present between the use of template and templateUrl that in many cases, just like this, are very hard to solve

[Narretz]

So, the question is if we intend to fix these or simply document these edge cases

[Narretz]

Duplicate of #14326