Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221)

domenic left a comment (whatwg/dom#221)

No objection, just warning you that it's a lot of work, because it involves, e.g., auditing the 882 `Document` references in HTML, not to mention other specs. (In many cases, leaving it as the shared base class would work, but for creation cases at the very least would need updating.)

I also believe that browsers aren't really interoperable here. E.g.:

- Last I looked, WebKit had made a lot of progress on moving things to `Document`, leaving `HTMLDocument` and `XMLDocument` mostly-empty derived classes. Whereas Chromium kept more things separately on `HTMLDocument` and `XMLDocument`.
- https://github.com/whatwg/html/pull/5104#issuecomment-558170849 points out some interop problems with SVG documents.
- In general updating the test suite to test which class is created where will be fun.

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

Message ID: <whatwg/dom/issues/221/2825931660@github.com>