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

Wow, there's been so many comments since I last visited.

I think it would be worth investigating alternative to the `is=""` attribute like "element-behaviors" or "element-features" or "custom-attributes":

- https://github.com/w3c/webcomponents/issues/662
- https://github.com/w3c/webcomponents/issues/727
- https://github.com/trusktr/element-behaviors
- https://github.com/matthewp/custom-attributes

(in fact, my `element-behaviors` is built on top of `custom-attributes` (that's how I made the `has=""` attribute concept there))

Please express your opinions on those ideas. They solve the issues that the `is=""` attribute has, plus they add more flexibility in API design that Custom Elements alone doesn't have.

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