[Bug 28720] Interop: browsers already handle duplicate "fake" xmlns declarations during XML serialization

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

--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(In reply to Domenic Denicola from comment #1)
> I am confused. As far as I can tell the given situation has several possible
> outcomes:
> 
> 1. <svg xmlns="http://www.w3.org/2000/svg" xmlns="anotherNS" /> (IE11)
> 2. <svg xmlns="anotherNS" /> (Chrome)
> 3. <a0:svg xmlns:a0="http://www.w3.org/2000/svg" xmlns="anotherNS" />
> (Firefox)
> 4. <svg xmlns="http://www.w3.org/2000/svg" /> (no current browsers)
> 
> You said that 1 caused an interop problem, which I take to mean a
> compatibility problem with an existing site. Why do you think introducing a
> completely new way, 4, would help? Wouldn't it be better to converge on
> either 2 or 3? (Or, ideally, 1, but if you've found content that breaks
> under that, then I guess that's no good.)

In many places (speaking of the spec algorithms generically) it made sense not
to follow any browsers due to weird edge cases that they all had. In other
words, this spec blazes new ground rather than just paving the cow paths.

In this specific case, I could re-write the spec algorithm to follow 3 which is
one possible "correct" solution, but 4 is also a "correct" solution and what
Edge is planning to implement given other namespace serialization fixes we've
made since IE11 to more closely follow this spec.

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

Received on Thursday, 28 May 2015 22:52:41 UTC