W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2009

[Bug 7510] Allow elements beyond just HTML, MathML, and SVG into SVG element

From: <bugzilla@wiggum.w3.org>
Date: Mon, 21 Sep 2009 11:27:30 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Mph3K-0006ra-Pu@wiggum.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-09-21 11:27:30 ---
If you're asking for parsing namespaces, then that's a non-starter, since it
would be far too easy for pages to end up stuck in one namespace in HTML5 UAs
while working fine in legacy UAs. It would also be an incredible amount of
complexity in the parser for more or less no benefit. This would be WONTFIX.

If you're _not_ asking for that, but _are_ asking for the results of the parser
to allow nodes that, when the same text is parsed as XML, would be allowed,
then the nodes wouldn't be in the same namespace as they would be if parsed
using an XML parser, so there'd be no way to allow them as far as I can tell 
we couldn't tell the difference between those nodes and illegitimate nodes.
This would be NEEDSINFO: I'd need an explanation for how to fix it.

If you're asking for nodes to be allowed when they are actually in the right
namespace in the DOM, then that's already the case, since HTML5 just defers to
SVG which allows namespaced content there. This would be WORKSFORME: it's
already allowed.

If you reopen this bug, please clarify which of the above you are asking for.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 21 September 2009 11:27:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:01 UTC