- From: Justin Fagnani <notifications@github.com>
- Date: Tue, 15 Jul 2025 16:55:01 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1000/3076124488@github.com>
justinfagnani left a comment (w3ctag/design-reviews#1000) If I may chime in as one of the community members with feedback and the original proposer of Declarative CSS Modules: I think for much the web components community the fundamental issue with the direction after the initial TAG review was that we don't need a _new_ way of sharing styles across scopes scopes, we need a way of deserializing an HTML payload into the _existing_ way that we already use to share stylesheets: `adoptedStyleSheets` arrays referencing `CSSStyleSheet` objects. I think it would be helpful to judge any proposal against the requirements I laid out in https://github.com/WICG/webcomponents/issues/939 , hopefully clarified a bit here: 1. The ability to serialize constructed stylesheets to HTML on the server, which must only apply where explicitly referenced. 2. The ability to populate a declarative shadow root's `adoptedStyleSheets` array by referencing serialized constructed stylesheets. 3. To support streaming SSR, the styles must be able to be written with the first scope that uses it and referenced in later scopes, regardless of tree structure or scope nesting. Or proposals and reviewers could disagree with those requirements, but they seem to be the critical ones among SSR users today, and alternate approaches like `@sheet` or fragment-referencing `<link>`s haven't met them yet. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1000#issuecomment-3076124488 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1000/3076124488@github.com>
Received on Tuesday, 15 July 2025 23:55:05 UTC