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

I don't think we can agree on that list of requirements because what constitutes a good design is often subjective and requirements can be arbitrarily restrictive as to favor one design over another. What we can agree on, however, are use cases.

For example, being able to add a new JS API on each row a specific table is one. `is` attribute solved this problem by extending `tr` element.

Creating a credit card input element which participates in the form submission and can be associated with a label element like other form control element is another.

And the list can go on. Note that not all use cases need to be addressed by a single proposal or solution. Often times, we need to look at the wholistic picture of the entire Web platform, and decide whether a given use case should be addressed in one or another because what we're designing here will stay with us for another 20 years, if not 50 years.

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