Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939)

I think [Open Issue #5](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/AtSheet/explainer.md#open-issues) is the key point here. When rendering DSD from the server, from a streaming HTML perspective, it would be useful to be able to emit stylesheets as they are "discovered" – regardless of whether that's in light DOM or shadow DOM. (And there would likely be several layers of shadow DOM.)

FWIW we have [a proposal for LWC](https://github.com/salesforce/lwc-rfcs/blob/nolan/ssr-dedup/text/0000-ssr-stylesheet-deduplication.md) to solve this style duplication issue, and it relies on being able to dynamically discover, render, and reference stylesheets without needing an external `<link>`. (This is kind of key, as it would introduce additional complexity to suddenly have a separate subresource to manage.)

> `<!-- Oh, here comes a component that needs some shared style. -->`

Slight wrinkle: component #<span></span>1 may not even "know" that its stylesheet needs to be shared until component #<span></span>2 comes along. Proactively setting up the first unique instance of a stylesheet for sharing is probably how most web component frameworks are going to want to do this.

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

Message ID: <WICG/webcomponents/issues/939/2599861729@github.com>