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

> My feeling is, that a solution cant be found, because there are no clearly defined requirements.

**Requirement:** we would like to extend native components for graceful enhancement, like it's possible already through the shipped `is=""`


> everyone just throws in their cases and expects web components to solve them.

**Use case:**  we would like to extend native components for graceful enhancement, like it's possible already through the shipped `is=""`


What is so difficult to understand and where is the confusion at all?

What can we do today with a `HTMLButtonElement` class?

Why is that not playing well like `HTMLElement` does?

Will that ever be fixed?

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