[Bug 17077] New: Spec for document.open() doesn't match reality when the parser is script-created

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17077

           Summary: Spec for document.open() doesn't match reality when
                    the parser is script-created
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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.)

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Saturday, 19 May 2012 10:34:59 UTC