Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)

In my first sentence I meant, that shadow-root-like styles seem to be a lot different than useragent-like styles. Besides implementation difference, functionality isn't the same. It's easier to override useragent (-like) style than it is to override styles in a shadow root (specificity and open vs closed).

The OP suggested shadow-like style, but what point does shadow-root-like style have except for styling the host? In this case, I think implementing a way to define useragent-like style per class is cleaner both from usage and implementation point of view.

And plus, maybe a shadow-like style could be just an additional way to override the useragent-like style. 

If someone wants to override the useragent-like style for many instances, they can, for example, make a subclass with new styles, and register a new element (f.e. in a scoped registry, and with the same name as before).

-- 
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/468#issuecomment-371213782