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

I've seen a lot of proposals and patterns tossed around. And throughout both use cases I have seen.

`<magic-juicy-button>`

Or 

`<button is="magic-juicy-button">`

What about forcing extended base elements to adhere to a tag naming constraint. That is, to say, if one wants to extend `<button>`, they would need to reference that tag as a name prefix.

`<table><sortable-tr>`

Or 

`<fancy-select>`

Or 

`<airhorn-button>`

Or 

`<accessible-nav>`

Or 

`<flexy-img>`

As a developer, there is no question to me what these extend and what primitive behaviors they use. And by enforcing these conventional constraints, the parser can pick up and understand the extended functionality, in addition to have a fallback. 



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