This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.whatwg.org/specs/web-apps/current-work/#dom-document-open says, in part: "If the document has an active parser that isn't a script-created parser, and the insertion point associated with that parser's input stream is not undefined (that is, it does point to somewhere in the input stream), then the method does nothing. Abort these steps and return the Document object on which the method was invoked." AFAICT, the part " that isn't a script-created parser" is bogus per the behavior of Firefox (tested trunk), Chrome (tested dev), Opera (tested Next) and IE (tested 9). See these demos: http://hsivonen.iki.fi/test/moz/document-open-during-network-parse.html http://hsivonen.iki.fi/test/moz/document-open-during-script-created-parse.html (Aside: It seems that the spec sides with WebKit and Presto rather than Gecko and Trident on the " and return the Document object on which the method was invoked" point.)
I wonder why I wrote that then. Weird.
This bug was cloned to create bug 17869 as part of operation convergence.
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-v2.html Status: Accepted Change Description: https://github.com/w3c/html/cd36e1deb09a229a753f71872f955d722cfa6c9f Rationale: accepted WHATWG change