transclude bug in IE

[maxisam]

Here is the example: plunker

It shows nothing in IE all version.

the way to walk around this bug is add space between "}}" and "</"

[petebacondarwin]

This seems like a weird way to use transclusion. Shouldn't you simply be terminating compilation instead: http://plnkr.co/edit/ZZPeHx?p=preview

[maxisam]

First of all, thank you for spending time on this. I think your answer is not an answer. It is more like a walk around.

It is just an example. It is not exactly how I used it. #6751 is the original case and it shows you why I used transclusion.

[onethread]

Got the same bug while doing transclusion with manually added ngRepeats.

In the function "addTextInterpolateDirective", node will be valid and correctly pointing to the text node when textInterpolateLinkFn is first called.

When the watch executes, node will be empty, and node[0] will fail. I'm not sure why. IE only.

return function textInterpolateLinkFn(scope, node) {
var parent = node.parent(),
bindings = parent.data('$binding') || [];
bindings.push(interpolateFn);
parent.data('$binding', bindings);
if (!hasCompileParent) safeAddClass(parent, 'ng-binding');
scope.$watch(interpolateFn, function interpolateFnWatchAction(value) {
node[0].nodeValue = value;
});
};

Example code:

This <a href="#" tooltip-placement="left" tooltip="On the Left!"> {{amount.name}} </a>
is contained in a dynamically generated ng-repeat. Adding spaces around the {{}} fixes it in IE.

[gustavohenke]

I was also suffering from that nodeValue problem, and I can confirm that using some spaces around {{ }} fixes it.

[Narretz]

This is the same issue as described here: #8659 (comment) and the next two comments.
Bottom line: don't compile the same node twice. It leads to unexpected results, and IE even throws.