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

Perhaps existing native elements should be re-worked so that any differences they have should rather be described (explained) by using class extension, and not using those other two methods (`is=""` and `options.extends`). An example of native elements that are defined with the same interface/class but with different `nodeName`s are `q` and `blockquote` which share the `HTMLQuoteElement` interface. We should attempt to describe the difference (if any) between these elements with class extension rather than `is=""` combined with `options.extends`. If there is no difference except for `nodeName`, then if they are both `instanceof` the same class that is fine too as long as the behavior for both elements is entirely defined in the shared class, and not by other means.

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