mass-move component to LC1

If it is taken into account then analyze more tescase, because for IE I noticed different behaviour (depending on how the tree was constructed).

<script>

	var container = document.createElement("div");
	container.appendChild(document.createTextNode("Text node 1"));
	container.appendChild(document.createTextNode("Text node 2"));
	
	var newEl = document.createElement("div");
	newEl.textContent = "Element content";
	container.appendChild(newEl);
	
	container.appendChild(document.createTextNode("Text node 3"));
	container.appendChild(document.createTextNode("Text node 4"));
	
	alert(container.childNodes.length);
	
	container.childNodes[2].outerHTML = " outerHTML ";
	
	alert(container.childNodes.length);
	alert(container.childNodes[1].data);

</script>

Firefox, Opera (Presto) alerts: 5, 5, Text node 2 << not merge anything

Chrome alerts: 5, 3, Text node 2 outerHTML Text node 3 << merge previous and next sibling (only text node) if exist

IE11 alerts: 5, 4, Text node 2 outerHTML << merge previous sibling (only text node) if exist, but if not exist and exist next sibling (only text node) then merge with them. This is not the same what we see in example from comment0.

But if merge will became standarized then what merge, only previous and next sibling (text node) or all contiguous Text nodes (https://dom.spec.whatwg.org/#contiguous-text-nodes)?

One more thing, IE11 also merge text nodes for Element.insertAdjacentHTML(), but Chrome and Firefox no.

<script type = "text/javascript">

	var container = document.createElement("div");
	container.appendChild(document.createTextNode("Text node 1"));
	container.appendChild(document.createTextNode("Text node 2"));
	container.appendChild(document.createElement("div"));
	
	container.childNodes[2].insertAdjacentHTML("beforebegin", " Parsed text");
	alert(container.childNodes.length);
	alert(container.childNodes[1].data);

</script>

Firefox, Chrome alerts: 4, Text node 2
IE11 alerts: 3, Text node 2 Parsed text

I'm opposite for merging text node in all this cases, they change node tree without possibility of control this behaviour. If someone want clean up tree then can use Node.normalize() or other way (how he want). There is no need to complicate this more.