[Bug 19431] Namespace of elements made via .createElement() in XML documents must be null

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

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |robin@w3.org

--- Comment #14 from Robin Berjon <robin@w3.org> ---
(In reply to Anne from comment #13)
> I would still prefer browsers to change as having something depend on MIME
> seems really counter-intuitive and has been a source of confusion in the
> past.
> 
> If everyone speaks up in favor of comment 12 though, I will play ball.

At this stage implementations haven't changed, is there any indication that
they will?

I sympathise with your point that having a single behaviour in all contexts is
nice for libraries, but I'm not sure it's the path forward. My (admittedly
somewhat dated) experience with trying to use off-the-shelf libraries in e.g.
image/svg+xml contexts when they were created and tested for HTML is that they
tend to fail for all sorts of reasons already.

This tells me it's just not something do, and I don't think we should be
encouraging it. We should be transitioning people to sending SVG and friends as
text/html (with matching syntax) and just have XMLDocument and its ilk
specified as they exist today and slowly pushed down the road to obsolescence.

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

Received on Tuesday, 6 January 2015 15:34:32 UTC