- From: Joshua Coffey <notifications@github.com>
- Date: Wed, 04 Mar 2020 15:49:42 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 4 March 2020 23:49:55 UTC
> > Forced encapsulation on Web Components destroys this. You can't write a stylesheet to theme the way a specific button looks anymore, because that button is a sub-component of a sub-component, thirty shadow DOM levels deep, and your sheet can't target it. > > That is not true? User stylesheets should apply to all elements in all shadow trees. This isn't what I've seen, but if you could elaborate I'd love to be wrong. My understanding is that Shadow DOM -- closed or open -- completely encapsulates all CSS except for custom properties and a few predefined properties. If any CSS bleeds through Shadow DOM it's because the component author specifically added support through theming or custom properties or some other manual method. Are you saying that user style extensions (eg Greasemonkey) are provided a native way to pierce the Shadow DOM, or that they provide their own method to do so through the extension? -- 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/864#issuecomment-594943385
Received on Wednesday, 4 March 2020 23:49:55 UTC