- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Oct 2014 23:43:33 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25225 Travis Leithead [MSFT] <travil@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Travis Leithead [MSFT] <travil@microsoft.com> --- (In reply to Simon Pieters from comment #4) > As a workaround you can do something like this: > http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2915 I can't view the above site today, but I assume this workaround is related to creating an HTML document (from within an XML document); something like: document.implementation.createHTMLDocument(), cloning the nodes to serialize as HTML into that document, and then invoking the innerHTML getter on an html container element...? Regardless of the use cases, I wouldn't want to extend XMLSerializer to handle this case, as that's an abuse of the name :) I suppose a new HTMLSerializer object would be the obvious corollary. Any browser implementations interested in an HTMLSerializer interface? Seems kinda redundant on the web (dominated by text/html documents); though I don't know the use cases for this in an XML data pipeline. -- You are receiving this mail because: You are the QA Contact for the bug. You are on the CC list for the bug.
Received on Monday, 13 October 2014 23:43:34 UTC