This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9649 - It doesn't look like any browser supports document.innerHTML
Summary: It doesn't look like any browser supports document.innerHTML
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2010-05-03 17:17 UTC by contributor
Modified: 2011-07-20 08:45 UTC (History)
9 users (show)

See Also:

Attachments

Description contributor 2010-05-03 17:17:28 UTC 
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
Comment 1 Anne 2010-05-04 00:44:35 UTC 
It's a new feature.
Comment 2 Henri Sivonen 2010-05-04 06:53:59 UTC 
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.
Comment 3 Anne 2010-08-04 06:43:21 UTC 
Fair enough. We are probably stuck with DOMParser...
Comment 4 Jonas Sicking (Not reading bugmail) 2010-08-04 18:02:29 UTC 
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.
Comment 5 Ian 'Hixie' Hickson 2010-09-10 09:10:09 UTC 
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.