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

> 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

This is [official documentation updated 22nd of May 2017](https://html.spec.whatwg.org/multipage/scripting.html#custom-elements-customized-builtin-example)

![screenshot from 2017-05-23 00-18-20](https://cloud.githubusercontent.com/assets/85749/26332256/66e66834-3f4d-11e7-8780-f8ea3384bfb2.png)

The polyfill is made by me and [it supports specifications](https://github.com/WebReflection/document-register-element#whats-new-in-custom-elements-v1).

Ths `is=""` behavior, as specified, has been used through this polyfill for years now.

The only people that don't see value in `is=""` are people that probably never used Custom Elements because me, like the rest of the developers that followed standards, believed the specification was good enough and went ahead using what was polyfillable.

All the rest of the statistics should have data to demonstrate numbers, because all these 95% of use case I'm reading about aren't nowhere backed by official data.

Do we have official data to open our eyse? I'd love to see it!

Thanks!

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