https://www.w3.org/Bugs/Public/show_bug.cgi?id=27976
Bug ID: 27976 Summary: [Custom]: type extensions should be available as custom tags, not only through <baseTag is="..."> Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglaz...@chromium.org Reporter: rjharmon0316...@gmail.com QA Contact: public-webapps-bugzi...@w3.org CC: m...@w3.org, public-webapps@w3.org Blocks: 14968 It seems to me that it's unnecessarily limiting to require that users specify the base tag type and also the extension tag. It seems to prevent the direct use of semantic tags which happen to use a non-generic html tag prototype. This might be simply a clarity issue, where in 11.2 Type Extension Example, you could specify that <button is=tequila-button> is equivalent to <tequila-button>. -- You are receiving this mail because: You are on the CC list for the bug.