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

> Not everyone can design stuff for the 95% of front-end web, a lot of us have to manage old crufty things too, don't forget about us. ^.^

As you implied: You are at the 5% end of the use cases that drive up "cost" (on the spec and/or DX and/or platform implementation) by a lot, if you want to cover these cases.
Since you mentioned Safari as one of your targets, i guess you rely on a polyfill for `is=""` (and a general CE polyfill for older safari versions). If we call that polyfill just "some micro framework that provides `is=""`", remove it from the spec and let the usage of this framework decide, if its a platform candidate. so we can defer this discussion until we have empirical proof that the `is=""` is widely accepted or just fills that one fraction of use cases that most webdevs will never face.

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