17216 2012-05-28 07:48:26 +0000 Fragment serialization doesn't handle the case when 'the node' is a void element yet has child nodes 2012-05-28 09:05:40 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Linux RESOLVED INVALID P2 normal --- 1 bugs ian ayg mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 68192 0 bugs 2012-05-28 07:48:26 +0000 If someone does <input>.appendChild(document.createElement("div")); per http://html5.org/specs/dom-parsing.html#innerhtml and http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#html-fragment-serialization-algorithm <input>.innerHTML would become "<div></div>". That doesn't look right, given that if <input> element is handled as a child of some element which is being serialized, the div element wouldn't end up to the innerHTML serialization. So, I believe http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#html-fragment-serialization-algorithm should handle the case when 'the node' is a void element and return empty string in such case. 68193 1 zcorpan 2012-05-28 08:03:39 +0000 Why? You can still set <input>.innerHTML = '<div></div>'. Since void elements can have children in XML or with DOM API, I don't see the point in changing this. 68194 2 bugs 2012-05-28 08:11:54 +0000 (In reply to comment #1) > Why? You can still set <input>.innerHTML = '<div></div>'. You can, but why is it expected that that actually parses something? > > Since void elements can have children in XML or with DOM API, I don't see the > point in changing this. It is strange inconsistency in the innerHTML serialization that it depends on the context where you use innerHTML what gets serialized. I mean, in some cases the contents of a void element is serialized, but in some cases it isn't. 68196 3 zcorpan 2012-05-28 08:26:10 +0000 (In reply to comment #2) > You can, but why is it expected that that actually parses something? Because it's what most browsers did when this was specified, I think. 68200 4 bugs 2012-05-28 09:01:38 +0000 Ok, Ms2ger gave yet another bad case. Ms2ger: <img><div><span></span></div></img>, what's div.innerHTML? So, ok, serialization is broken by design. I don't care enough, and I can close this bug. 68201 5 ayg 2012-05-28 09:05:40 +0000 FWIW, from Live DOM Viewer: <!DOCTYPE html> <img> <script> document.body.firstChild.appendChild(document.createElement("div")); w(document.body.firstChild.innerHTML); </script> This outputs the empty string in Chrome 21 dev and Opera Next 12.00 alpha, and "<div></div>" in IE10(ish) and Firefox 15.0a1.