Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308)

Thanks @domenic, I've taken a look at those issues and [virginamerica.com from 2011](https://web.archive.org/web/20110901145632/http://virginamerica.com/). The [problem](https://gist.github.com/foolip/5dad6b61d8ee36e61d829dbf112c153b#file-globalscriptfile_08232011-pretty-js-L180) (from [Sarissa 0.9.6.1](http://sarissa.cvs.sf.net/viewvc/sarissa/sarissa/sarissa.js?revision=1.25&view=markup#l256)) was `XMLDocument.prototype.onreadystatechange = null` and the fix was [`[LenientThis]`](https://github.com/whatwg/html/commit/8f58ef7332a9fb28472ec14fd229ecc15d7e0052).

This was in a non-IE codepath, "applewebkit"-sniffing actually wasn't involved here.

Note that Sarissa by itself doesn't require the existence of `XMLDocument.prototype.load`, it just wraps it as @bzbarsky [described](https://www.w3.org/Bugs/Public/show_bug.cgi?id=14037#c14). But it's only if some other script calls `xmlDoc.load()` that it matters, and virginamerica.com didn't AFAICT. It also doesn't seem to matter for Sarissa if `XMLDocument` is an alias of `Document` or a separate interface.

The question then remains, does Gecko need `XMLDocument.prototype.load` (and `async`) for compat? If it does, then it must be in some Gecko-only code path. Researching this with HTTP Archive would be very hard, any change for use counters here?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/308#issuecomment-247815705