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

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

It's not hard to understand at all.  But it's only useful 0.0000000000000000001% of the time, if ever, we don't really know because there are 0 compelling use cases.  Everything talked about so far can just as easily be just as easily solved with the gazillion microframeworks already out there, and as we have pointed out there are plenty of drawbacks to pretending that this is a solution for web developers, including fracturing the mental model for what a web component is and how it works.

> Will that ever be fixed?

There is no problem to be solved that has not already been solved.  The 'is' attribute is just asking for a different solution to stack on top of the 100s of solutions that currently exist.

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