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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7510





--- Comment #14 from Shelley Powers <shelleyp@burningbird.net>  2009-09-22 21:48:52 ---
(In reply to comment #13)
> (In reply to comment #12)
> > Ian:  Thinking a little more - why couldn't these errors be dropped when the
> > parser's insertion mode is "in foreign content" i.e. a change in the parser
> > spec?  
> 
> The HTML spec doesn't say that these are errors, the SVG spec does. The HTML
> spec is only relevant here because it is the spec that is failing to put the
> elements in the expected namespaces.
> 
> 
> > What's the value in reporting those errors?  Is it to help people who misspell
> > 'rect' etc?
> 
> Yes.
> 

Then one can assume that if elements are referenced without a namespace they're
from the SVG namespace, and handled accordingly. Frankly, though, such
validation should occur with an SVG specific validator, not one that's HTML5. 

That's not what this bug is about. This bug is deferring to the SVG
specification about what is or is not conforming. 

The HTML5 specification should ignore namespaced contents of the SVG element.
That's what the SVG specification states: they should be ignored. 

Insert into the HTML5 specification:

The SVG specification states that namespaced elements not part of the SVG
specification, and not included in a foreignObject element should be ignored.
These namespaced elements will be ignored in HTML5. They are considered neither
conforming nor non-conforming from an HTML5 perspective.

Then all validator creators, not just the one, will understand what to do when
it comes across unknown namespaced elements within the SVG element. They will
ignore them.


-- 
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 Tuesday, 22 September 2009 21:49:01 UTC