[w3c/webcomponents] Proposal: Allow custom elements to be in any namespace (#634)

In the current spec custom elements can only be in the namespace http://www.w3.org/1999/xhtml 
and without using `is=""` derive from `HTMLElement`. It is desirable to have custom elements in other namespaces
* Create custom SVG elements in the SVG namespace which derive from `SVGElement`
* Create elements in your own namespace using XHTML which derive from Element

My proposal is to add  a ‘namespace’ property to ElementDefinitionOptions to specify in which namespace the custom element should be placed. I created [an issue](https://github.com/w3c/webcomponents/issues/328) before for Custom Elements v0.
# Advantage
If the namespace isn't used by the browser for rendering (e.g. http://www.w3.org/1999/xhtml or http://www.w3.org/2000/svg) the dash requirement for new custom element tag names can be removed.
# Use cases
This way it is possible to create polyfill XHTML extensions such as XForms, MathML or X3D using custom elements.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/634