Re: [w3c/webcomponents] Customized Autonomous Elements (#750)

The is="" model is intended for allowing built-in browser features of the built-in element to still work. It's not intended as a way of allowing you to write one tag name in your CSS instead of two.

For autonomous custom elements, whether or not they inherit from anything between themsleves and HTMLElement is an implementation detail. Inheriting from some other autonomous custom element is the same as inheriting from any other random class. (As long as you obey the requirement that HTMLElement end up in the prototype chain at some point.)

Finally, it's worth noting that is="" only works with a single level of inheritance; since autonomous custom elements can have arbitrary inheritance chains, it's not a good fit there.

Those are the reasons I remember for this. Basically, the model does not fit well, and the benefits are tiny (writing `x` does not save many characters over writing `x, y`).

Since we're unlikely to change this, let me close the issue. But, I'm happy to continue discussing in the closed thread.

-- 
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/750#issuecomment-384663104