12584 2011-05-02 22:41:40 +0000 outerHTML should probably merge with adjacent text nodes if applicable. IE seems to do this to some extent, and WebKit just changed to do it: <https://bugs.webkit.org/show_bug.cgi?id=52686> This test shows behavior for outerText and outerHTML: <http://so 2015-10-02 01:23:55 +0000 1 1 1 Unclassified WebAppsWG DOM Parsing and Serialization unspecified Other other NEW P3 normal --- 11204 1 contributor travil annevk ayg crimsteam ian keithbrunson mike Ms2ger public-html-admin public-html-wg-issue-tracking public-webapps shadow2531 www-dom public-webapps-bugzilla oldest_to_newest 47849 0 contributor 2011-05-02 22:41:40 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/apis-in-html-documents.html Section: http://www.whatwg.org/specs/web-apps/current-work/#outerhtml Comment: outerHTML should probably merge with adjacent text nodes if applicable. IE seems to do this to some extent, and WebKit just changed to do it: <https://bugs.webkit.org/show_bug.cgi?id=52686> This test shows behavior for outerText and outerHTML: <http://software.hixie.ch/utilities/js/live-dom-viewer/saved/971> (Opera never merges, IE9 merges for outerText and partially merges for outerHTML, WebKit now fully merges for both, Gecko doesn't implement either) Posted from: 68.175.61.233 User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.12 Safari/534.30 53805 1 mike 2011-08-04 05:17:30 +0000 mass-move component to LC1 123421 2 crimsteam 2015-10-01 18:55:47 +0000 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)? 123432 3 crimsteam 2015-10-02 01:23:55 +0000 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.