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

Just to be clear, I'm fine with `:host` and `:host-context`, as it solves the majority of use-case I'm aware of. I don't want to undermine the consensus.

----

That's just mental experiment to [broaden supported use-cases](https://github.com/w3c/webcomponents/issues/468#issuecomment-371453775).


> Host's descendant nodes are out of scope in any case, **from the perspective of** a style rule defined in a **shadow tree**.


But if we would think of the use case of "Provide a lightweight mechanism to add styles to a custom element" - OP title, does not mention shadow root necessarily.

So if we would look from the perspective of [Domenics 1.](https://github.com/w3c/webcomponents/issues/468#issuecomment-371368425)
> It introduces a way to add your own user agent stylesheets for a custom element, at a new-ish cascade order that is basically the same as UA stylesheet order but lives after existing UA stylesheets, is scoped to only apply inside instances of this custom element, and interprets `:host` as applying to the custom element.

`:scope` could be the element, not it's "some imaginary shadow context" 


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