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

> FWIW, we're against subclassing subclasses of HTMLElement (e.g. HTMLInputElement, etc...) for various reasons, so WebKit isn't going to support this feature anyway. Extension of builtin elements are much better served with mixins.

> One fundamental problem is that subclassing a subclass of HTMLInputElement or HTMLImageElement often leads to a violation of the Liskov substitution principle over time. 

True, which is why we should avoid subclassing when we can, but I think it's needed in order to fix the mistake that was made with `q` and `blockquote`. Maybe we should leave `HTMLQuoteElement` for the `q` tag, and make a new `HTMLBlockQuoteElement` for the `blockquote` element. That would help explain the behavior (for the web manifesto).

Otherwise, how does the web manifesto explain the difference between `<q>` and `<blockquote>`? I.e. How would the `customElements.define()` calls for `q` and `blockquote` differ in order to theoretically satisfy the web manifesto?

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