9649 2010-05-03 17:17:28 +0000 It doesn't look like any browser supports document.innerHTML 2011-07-20 08:45:43 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#innerhtml NE P3 normal LC 1 contributor ian annevk hsivonen ian jonas mathias mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35379 0 contributor 2010-05-03 17:17:28 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#innerhtml Comment: It doesn't look like any browser supports document.innerHTML Posted from: 81.245.240.211 by ms2ger@gmail.com 35387 1 annevk 2010-05-04 00:44:35 +0000 It's a new feature. 35390 2 hsivonen 2010-05-04 06:53:59 +0000 Given that DOMParser already exists on the XML side and we prefer XHR over Document.load(), I'd like to see the rationale for introducing this new feature instead of making DOMParser support text/html. 37223 3 annevk 2010-08-04 06:43:21 +0000 Fair enough. We are probably stuck with DOMParser... 37230 4 jonas 2010-08-04 18:02:29 +0000 The situation for .load is significantly different since it changes the URI of an existing document. At least it raises confusion about what the URI should be. I see value in being able to replace the contents of an existing document without having to use document.open hacks or having to manually set up a root element and then use innerHTML on that. 38805 5 ian 2010-09-10 09:10:09 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: DOMParser is way more complicated than necessary.