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

I use mixins since about ever and I've never had an issue with the `is` attribute.
Like me, many other projects based on `is` attribute never had issues neither, and I'm personally tired of APIs that ships, and work, for years, and then break all of a sudden due people that never used those features they want so desperately remove.

The `is` attribute is ugly, but it works very well since its first appearance.

With Edge on Chromium, only Safari is missing the train but the polyfill for Safari only works fast and we'll, plus Safari is used on powerful devices so performance is not an issue.

This thread should be closed, imo.

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