Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)

@rniwa 

>  there could be an intense of HTMLAnchorElement whose local name is not a.

I think you meant "instance" instead of "intense"? This seems to be the reason why `is=""` exists, making it possible to create new elements that extend from elements that inherit from the same class, but that possibly have new behavior added to them in the definition. This is also the reason for the `{extends: "element-name"}` (I am calling it `options.extends`), which effectively accomplishes the same thing.

I am against both of those. We have ES6 classes now, and that should be the defacto way to define extension, without the other two (possibly confusing) mechanisms.

Existing native elements should be modified so that any differences they have (for example, any native elements that are defined with the same prototype) should rather be described by extending using class extension, and not any other method.

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