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: Fri, 18 Sep 2009 20:58:19 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MokX5-0007Bv-Vq@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7510


Shelley Powers <shelleyp@burningbird.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |




--- Comment #2 from Shelley Powers <shelleyp@burningbird.net>  2009-09-18 20:58:19 ---
Right now, if you have RDF/XML in the metadata element, or Inkscape names[aced
attributes elsewhere in the SVG, Validator.nu throws some nasty errors. It does
so, because, according to the validator's author, these are not allowed in SVG. 

I would like to see namespaces supported, if we're supporting XML, and SVG _is_
XML, but I'm not pushing for that here. What I'm asking for is something in the
specification that the validity and conformance of the SVG is defined in the
SVG specification. HTML5 conformance checkers should ignore namespaced elements
they don't recognize. 

As for how namespaced elements are handled by the HTML parser, which would
result in things like localname of dc:title, I'm not asking for a change in
this behavior. I'll recommend people use SVGWeb if they realistically want to
work with SVG/XML in an HTML document. For now, I don't want conformance errors
triggered on perfectly valid SVG.


-- 
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 Friday, 18 September 2009 20:58:30 UTC

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