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

> On the other side, if I need to ban a feature in a large engineer team, I would choose to ban the normal custom element, and only use is to extend. Because most average developers do not have enough knowledge and experiences on components design, which means they are very likely to produce a leaky abstraction, or do something wrong (for example, raise a11y issue). And is way is much safer for them. 

And what are you doing in all the cases where the `is` attribute is not applicable because the element can't be downgraded to something, which is essentially 99.9999999% of all developer cases that custom elements were developed for to start with?

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