[Bug 17216] New: Fragment serialization doesn't handle the case when 'the node' is a void element yet has child nodes

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17216

           Summary: Fragment serialization doesn't handle the case when
                    'the node' is a void element yet has child nodes
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: Olli.Pettay@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 28 May 2012 07:48:34 UTC