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

> Then that should be all that is necessary in order ensure that that element knows that it is a button and that element should have all the features that (Accessibility, etc.) of the native button element. If we get the DRY part right, then web developers get a predictable, consistent, and symmetric programming paradigm to work with.

And how does that call back to non-JS browsers like elinks?  Would the `<my-button>` work in elinks?  No it would not, hence why `<button is="my-button">` is necessary if you want progressive-enhancement.  In the button case you could wrap it of course, but you cannot do that in all cases, like tables (or templates in tables for JS use, but just tables for non-js 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-265803447