[Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21886

--- Comment #15 from Dominic Cooney <dominicc@chromium.org> ---
(In reply to comment #14) 
> We still need to do some prototype chain walking, because we need to infer
> the namespace for the custom element (it really is either HTML or SVG
> namespace).

I think the spec should only allow type extensions for SVG. Then all custom
tags will be HTML and no prototype walking is required.

My thinking is this: SVG basically gives up when it encounters an unknown
element (it doesn't render that element's children, for example.) Assuming
you're using SVG to draw something, you're gonna want to use a specific tag (at
least <g>, which is a nice neutral one.)

If you think custom tags are important to SVG, perhaps we should define custom
tags to be extensions of SVGGElement (ie <g>, note the extra G) and not
SVGElement?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 30 May 2013 00:53:49 UTC