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

to some extend, `jQuery` has somehow "polyfilled" way less perfromant browsers for more than a decade so I'm OK to keep polyfilling 'till they add the feature.

You? Of course you can chose to do whatever you like, and just to be clear, the `is` attribute is not blocking anyone, it's just in specs.

WebKit already shipped Custom Elements v1 without is, and while Chrome is bringing it in soon, since it's been assigned for a while now, you can see `is` or not `is` nobody is really blocked here.

If MS will ship Custom Elements without `is` and they'll implement later on it's fine for me. Have I mentioned I've used it for years now without any issue whatsoever?

Chose what you need for your business. If you don't need `is` don't use it but don't come here saying nobody needs it because that's simply a lie and outside reality.

You said you knew about `is`, and probably Custom Elements, just recently with V1, many here have been using CE for years now so maybe we have reasons to ask other vendors to swallow its imperfections and move on bringing in its awesomeness.

Now I don't think me and you have much more to tell so, have a nice day/evening. Let's keep this thread open for discussions.

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