- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 May 2015 22:41:54 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28720
Domenic Denicola <d@domenic.me> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |d@domenic.me
--- Comment #1 from Domenic Denicola <d@domenic.me> ---
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.)
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 28 May 2015 22:41:56 UTC