- From: Luis Pato <notifications@github.com>
- Date: Thu, 14 Mar 2024 10:53:59 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/909/1998017830@github.com>
I am really sorry i missed the call the other day... :( I am not sure opening the components to outside styles is the silver bullet people often mention. Maybe for something like a reset or "tag" styles, but as soon as the component internal elements also have classes it is very unlikely that the classes from the page and the component will match. For instance a page using UIKit, Bootstrap or Bulma would not have the same classes as as component created using BEM CSS. So a `button button--primary` would not necessarily automatically get the correct styles... Nonetheless i think we all agree is it something that could be very useful. I wonder if there should be some way for component authors to create "private" and "public" parts of the component (in regard of being affected by the outside styles). I am a big fan of the `:part`. I just wish there would be a way to select also child elements of the :part. Is that what `@scope` would do? (sorry, i have never used `@scope`, must look into it...) I also like the idea mentioned by @robglidden to allow users to add something like `shadowlayers="buttons, inherit.BETTER-BUTTONS"` to a component so it inherits some layers styles. Would this also work on composed / nested components? -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-1998017830 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/1998017830@github.com>
Received on Thursday, 14 March 2024 17:54:03 UTC