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

> My proposal is to find use cases which can't be satisfied without `is`

You have these use cases since the very beginning of this thread and @treshugart [just added few](https://github.com/w3c/webcomponents/issues/509#issuecomment-281547850).

> It is pretty clear to me at this point that many people have different opinions on how to approach this

we're just speculating on what could be the implementation of what **you** proposed but so far the entirety of the Web did just fine with `is=""` attribute in V0 and polyfilled V1.

>  it's probably best to let Web developers experiment it first

We cannot extend native builtins so how/what are we supposed to experiment, exactly?

The [data-boo](https://github.com/WebReflection/ce-examples/tree/master/ce-data-boo) is an experiment born as a joke that wraps native builtins inside their related CE, where it's possible, yet it would use promotion or upgrade builtin elements where encountered because, in case it's not clear yet, we cannot:

  * extend native builtins
  * define table rows as custom elements
  * use smarter img tags
  * inherit aria

etcetera ...


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