- From: Domenic Denicola <notifications@github.com>
- Date: Thu, 24 Mar 2016 08:11:56 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 24 March 2016 15:12:23 UTC
In general I do think it's a bit weird that type extensions rely on a lot of the same constraints and infrastructure as custom tags, when there's no real reason to do so. E.g. maybe in my ideal world you'd have `customElements.define("custom-tag", CustomTag)` and `customElements.defineExtension("button", "plastic", PlasticButton)`, instead of lumping them both together with `customElements.define("custom-name", CustomTag, { extends: "button" })`. But I'm not sure it's worth the churn. Especially since there's a weak argument that the hyphen encourages namespacing, anyway. --- 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/201#issuecomment-200880139
Received on Thursday, 24 March 2016 15:12:23 UTC