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

> it could quite easily if there was someway to hint to the CSS engine about the custom element directly on the constructor

ehr ... like what? CSS and HTML are a separate world, which is why `customElements` is a registry exposed to JS land in order to hook elements into DOM one.

Let's not make this impossible for everyone to achieve in less than year, maybe?

We already have a registry for elements, extending it for behaviours/composed interfaces seems easier for everyone.


> I'd much rather leverage existing JS language semantics

decorators are Stage 2 and not even close to be shipped.

I'd rather be pragmatic and move the Web forward, specially because any procedural way can be easily extended later on through decorators. That's the whole point, giving us the ability to simplify otherwise cumbersome low-level patterns, which is why we all wrapped CustomElements API somehow, right? 😉 




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