W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2012

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 May 2012 08:11:55 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1SYv3T-0002P5-7p@jessica.w3.org>

--- Comment #2 from Olli Pettay <Olli.Pettay@gmail.com> 2012-05-28 08:11:54 UTC ---
(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.

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 08:12:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:29 UTC