- From: <bugzilla@jessica.w3.org>
- Date: Wed, 09 Oct 2013 12:05:33 +0000
- To: www-svg@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23468 Bug ID: 23468 Summary: Define that unknown elements implement SVGElement Product: SVG Version: SVG 2.0 Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: SVG Document Object Model (DOM) Assignee: schepers@w3.org Reporter: simonp@opera.com QA Contact: www-svg@w3.org Consider <!doctype html> <svg><x> What interface does the <x> element use? Spec says [[ Every Element object that corresponds to an SVG element (that is, an element with namespace URI "http://www.w3.org/2000/svg" and a local name that is one of the elements defined in this specification) must also implement the DOM interface identified in element definition. For example, in The ‘rect’ element, the SVGRectElement interface is identified. This means that every Element object whose namespace URI is "http://www.w3.org/2000/svg" and whose local name is "rect" must also implement SVGRectElement. ]] http://www.w3.org/TR/SVG2/svgdom.html#ElementsInTheSVGDOM but this doesn't cover the <x> element above, which I think means it must implement the Element interface. Blink and Gecko don't do that; they use SVGElement interface for unknown elements in the SVG namespace. I think the spec should require that all elements in the SVG namespace with a local name that is not a defined SVG element in the spec, must implement the SVGElement interface. (HTML uses an "HTMLUnknownElement" interface for unknown elements, but that's just because legacy content required it; we don't need to copy that for SVG.) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 9 October 2013 12:05:35 UTC