- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Mar 2014 22:03:27 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25168
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> ---
Makes sense, thanks for the tip.
I just noticed today that the innerHTML/outerHTML APIs specify throwing
behavior for nodes in XML Documents that don't meet the rules outlined in:
http://www.w3.org/html/wg/drafts/html/master/single-page.html#xml-fragment-serialization-algorithm
I think the right plan moving forward is to embed these throwing rules into the
algorithm, made conditional on a flag. Then serializeToString would not set the
throwing flag to be consistent with the way it works today, but
innerHTML/outerHTML would. Then, if we want to, we could extend the capability
of serializeToString to allow passing a flag to enable the throwing behavior.
This way applications that want the strict serialization via this mechanism can
get it.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 27 March 2014 22:03:28 UTC