Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

First, please be aware of the [Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/) that governs your participation in this repository. Name calling people as "the perfect-seeking enemies of good" would not result in any productive conversation.

There are many technical reasons we strongly opposed to having the is attribute. Use cases presented for `is` attribute such as being able to make custom elements accessible and participating in form submissions are valid. What we don't agree is the approach taken by `is` (as we've explained many times over the last four years).

For accessibility, we've suggested adding the capability to define the default accessibility role in options to `customElements.define`, and have been working with other vendors on [accessibility object model](https://wicg.github.io/aom/spec/). For form submissions, [we've been advocating for a generic mechanism to make any element participate in a form submission](https://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0448.html).

-- 
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-280886652