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

> browsers can still be supported without needing to write duplicate custom sites for them

That's the key.  And that's why I keep asking for simple examples of web content that uses custom elements and the `is` attribute, but will still provides a decent user experience without javascript.  If that's possible then there is a point here, so the more user stories / cases we collect the better the argument gets.

I think the reason browser vendors are [expressing a distaste](https://developers.google.com/web/fundamentals/getting-started/primers/customelements) for the `is` attribute is because it sounds nice in theory, but will actually never be used by 99.99% of developers because the will just be using things like `<paper-button>` instead.  It's well document, provides rich functionality, and it's an element that's easy to understand and use.

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