W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 14037] New: Should XMLDocument be standardized

From: <bugzilla@jessica.w3.org>
Date: Tue, 06 Sep 2011 04:16:36 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-14037-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14037

           Summary: Should XMLDocument be standardized
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: bzbarsky@mit.edu
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


All of Gecko, WebKit, and Presto have a window.XMLDocument.  It has pretty
different behavior in the three in some ways, but its mere existence is sniffed
for by some libraries (e.g. Sarissa).  See
https://bugzilla.mozilla.org/show_bug.cgi?id=684671#c2 for the gory details.

Should this object exist?  If so, should it be an interface, or just some
random object?  If the former, what things should live on this interface, what
does it inherit from, etc.

http://html5.org/specs/dom-parsing.html defines an XMLDocument inheriting from
Document, which seems to not be web-compatible if onreadystatechange has a
typical webidl setter on Document.prototype.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 6 September 2011 04:16:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:18 UTC