Providing the original document tree before transformation in HTMLDocument.responseXML makes sense. In that case, the Document returned should be immutable, just as a DOMString is; I am not sure how to declare it in IDL.
Chris _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Weston Ruter Sent: Wednesday, October 29, 2008 8:35 PM To: Kristof Zelechovski Cc: [EMAIL PROTECTED]; Ian Hickson; Anne van Kesteren Subject: Re: [whatwg] Implement XMLHttpRequest interface subset onHTMLDocument This is not completely strange or unexpected construct, since window == window.self. Furthermore, having a HTMLDocument.responseXML would be useful in the case that an XSLT stylesheet outputs HTML, plain text, or something else; in such a case, it would be very useful to get the original responseXML. Note that I don't envision this responseXML being any sort of shadow DOM; I mean, if XSLT did transform the XML data, making a change to responseXML would not cause the XSLT engine to re-parse the updated responseXML. Maybe this would be useful, but it seems overly complicated. On Wed, Oct 29, 2008 at 12:26 PM, Kristof Zelechovski <[EMAIL PROTECTED]> wrote: The meaning of "HTMLDocument.responseXML" looks a bit strange and unexpected: a property of an object bound to the object itself by definition. I would suggest leaving that one out. Chris _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Weston Ruter Sent: Wednesday, October 29, 2008 8:19 PM To: Kristof Zelechovski Cc: [EMAIL PROTECTED]; Ian Hickson; Anne van Kesteren Subject: Re: [whatwg] Implement XMLHttpRequest interface subset onHTMLDocument If the interface were implemented as-is, document.responseXML would just be a reference back to the document object. So if the document is XML, then document === document.responseXML On Wed, Oct 29, 2008 at 12:14 PM, Kristof Zelechovski <[EMAIL PROTECTED]> wrote: What should the property "HTMLDocument.responseXML" represent? Chris
