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

> Devs A, B, and C all add various bits of native button functionality to their 'buttons', some based on need, others based on time and effort, but all of them, even the ones who try to achieve nearly the same thing, will result in heterogeneous native-recreation attempts. What you end up with is hundreds of common button-esque implementations that are unintentionally jagged, just-off versions of native, expected button functionality.

But how would that be different in the world of `is`? One can override some aspects of builtin elements using `is` without fully making other aspects compatible. For example, you can just attach a shadow root on a builtin element, insert a bunch of divs to change the appearance, and then forget to specify ARIA. The browser engine then has no way to making it accessible.

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