fix getContainedComponents in IE 11

[KuroGuo]

No description provided.

[yyx990803]

Is it possible to provide a repro of the error before the fix?

[KuroGuo]

In IE, nextSibling returns a text node, but text node has no method 'contains'.

[yyx990803]

Thanks for the fix! The situation can be a bit more complicated though, in the case where the component is a block instance (thus its $el can be a TextNode too).

So I think it's better to change the check to:

if (
  cur === c.$el || // both are textNodes
  (cur.contains && cur.contains(c.$el)) // other situations
) {
  return true
}

[yyx990803]

we still need to check the case where cur === c.$el, because in IE cur.contains is not present if cur is a textNode

[yyx990803]

Merging so you can get credit, I'll fix with tests. :) thanks

[salazr]

FYI, we had the same issue, and came to the same workaround in testing (+cur.contains(el) on the if directive), but kept digging, and it was triggered by IE9 when doing v-if inside a < template > tag.

[yyx990803]

yep, the whole IE family doesn't implement contains for text nodes. In the spec contains is part of the Node interface, which should be available for text nodes as well, but oh well, it's IE...