[Bug 22960] Document, XMLDocument, HTMLDocument, oh my

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

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
> Virtually all browser vendors disagree with merging:
> https://bugzilla.mozilla.org/show_bug.cgi?id=897815
> https://code.google.com/p/chromium/issues/detail?id=238368
> https://bugs.webkit.org/show_bug.cgi?id=110772

Those bugs are still open. I wouldn't characterise that as disagreeing, just
being cautious, as they should with something this drastic. This is the same
thing we went through (correctly and appropriately) with the HTML parser.


> > It doesn't make sense to have separate SVGDocument and HTMLDocument objects.
> > You can have HTML in SVG and SVG in HTML.
> 
> Unfortunately, it's common that browsers are doing something totally
> nonsensical and the spec will have to document the nonsense.

Sure, but that's not the only choice. Here in particular it doesn't seem to be
the right choice, even.

There's maybe work to do — for see this thread:
   http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Oct/0062.html

But just sticking with the old solution of separate SVGDocumetn and
HTMLDocument objects just doesn't work.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 9 October 2013 19:41:48 UTC