Remove browser sniff in compile.js

[david-mark]

Note: for support questions, please use one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.

Do you want to request a feature or report a bug?

Neither.

What is the current behavior?

Browser sniff for IE 11 is used instead of a feature test.

// Support: IE 11 only
// Workaround for #11781 and #14924
if (msie === 11) {
    mergeConsecutiveTextNodes(nodeList, i, notLiveList);
}

Direct test would be something like this:

var el = document.createElement('span');
document.body.appendChild(el);
span.innerHTML = "— {{ 'foo' }}";
var problemWithSplitTextNodes = span.childNodes.length > 1;
document.body.removeChild(el);

Do that once during initialization (or first time through).

Would fix in all browsers (including future browsers) and configurations that may exhibit this quirk (would have to check the specs to determine if it is at odds with standard recommendations).

[gkalpak]

Interestingly, your test fails on IE11-in-IE10-mode (although I think only IE11 was affected by the issue).
I would not mind changing it to do feature detecting, but only if we can eliminate false positives (because this is not an internal change; it affects the public API and starting to concatenate text nodes could break people's apps).

[Narretz]

We don't support the IE-in-IE modes, so I'm okay with changing it, although I don't think it's high priority. I agree that browser sniffing is bad, but so far it works for these cases.