Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)

As far as i know, there is a huge fraction of developers that embrace the cascade (One small example is the `flow` utility class (https://piccalil.li/quick-tip/flow-utility/) or more general the owl selector.), but still want to use custom elements with slots for the interactive content parts of a page. But the button (design system) example is also a good one.

I personally never had the need in any project to use shadow dom like style encapsulation, you can write good side effect free css without encapsulation, even if it would come in handy sometimes, but for this case the `@scope` feature seems more appropriate.

Maybe i'm understanding this discussion wrong, but this is not only about web components used as third party elements (ie. user/author relation), it is also about author/author relation.

The layer idea seemed like a good idea at first, but it is not compatible with external stylesheets that do not use layers, that will be there for years to come in big projects. Also i feel layers are it's own feature and shouldn't be mandatory to solve this problem. The same like you can use all the feature that make a web component also on its own.

Thanks for all the ideas, but none of them feels like it is solving, the use cases i can think about. Nor the reason why teams i work in, choose light dom custom elements (even if it means no slots) instead of shadow dom web components.

About the "inject the global stylesheet" into the web component topic: There is already finegrained css codesplitting to optimize for performance on a global level, adding another logic layer, for deciding what css chunk should go into which web component, doesn't seem feasable without adding far more complexity from this perspective.

An easy option to "open" the shadow dom, on a web component level seems to be the best option here, although i understand it is not easy to implement for browser vendors. (At least for Safari.)

Hopefully this add's a few more usecases to the discussion, otherwise feel free to correct me :smile: 


-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/909#issuecomment-1885806638
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/909/1885806638@github.com>