- From: Zambonifofex <notifications@github.com>
- Date: Sat, 11 Jun 2016 15:19:39 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
Received on Saturday, 11 June 2016 22:20:09 UTC
Also, like @trusktr said, if this and whatwg/html#896 become a thing, I think it’ll be possible to remove altogether the `extends` property from the `options` argument. We would then write `customElements.define("awesome-button", class extends HTMLButtonElement{}, {})`, which I really like. Offering this as an alternative to the current way of defining extending native elements — allowing user agent developers and authors to choose which they want to use — is the best solution in my opinion. As @trusktr said, _“I think ‘breaking the web’ might actually fix the web in the long run”_. --- 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/509#issuecomment-225397643
Received on Saturday, 11 June 2016 22:20:09 UTC