This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17031 - <foreignObject> is wrongly marked as invalid when outside <switch>
Summary: <foreignObject> is wrongly marked as invalid when outside <switch>
Status: NEW
Alias: None
Product: HTML Checker
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-10 14:28 UTC by Leif Halvard Silli
Modified: 2012-05-10 14:28 UTC (History)
0 users

See Also:

Attachments

Description Leif Halvard Silli 2012-05-10 14:28:59 UTC 
Problem: The HTML5 validator stamps <foreignOBJECT> as invalid, unless is occurs as child of the <switch> element.  By contrast, W3's SVG specific validation service considers it as fully valid even without the <switch> element.

What does the spec say?  Well, according to HTML5, then HTML5 supports SVGTiny12. And SVG Tiny 1.2 says:

]] Usually, a 'foreignObject' will be used in conjunction with the 'switch' element and the 'requiredExtensions' attribute to provide proper checking for user agent support and provide an alternate rendering in case user agent support is not available. [[
See: http://www.w3.org/TR/SVGTiny12/extend.html#ForeignObjectElement

Thus, according to the spec, there is perhaps a  recommendation to use <switch>, but there is no requirement to use <switch>.