- From: Kurt Catti-Schmidt via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Apr 2025 16:28:02 +0000
- To: public-css-archive@w3.org
> * [In 2011, inline module declarations were proposed for ES Harmony Modules](https://web.archive.org/web/20160203104148/wiki.ecmascript.org/doku.php?id=harmony%3Amodules) at one point. > * See also a [2020 proposal for anonymous inline ES modules](https://gist.github.com/littledan/f7c1d1abf0e51ad4b526a8eadb2da43b) from [@littledan](https://github.com/littledan). > * Of course, inline ES modules would face similar problems as `@import` in `@sheet`; see MicrosoftEdge/MSEdgeExplainers#936. > > The only question I have left about `@sheet` itself is how it can align more with Declarative CSS Modules and [Declarative Shadow DOM Style Sharing](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ShadowDOM/explainer.md). > > * This seems uncertain especially given that the Edge explainers say that “we'll be prioritizing only one of these two [three?] in the immediate future”. Thank you for bringing this up. We see value in both `@sheet` *and* CSS Modules, but are currently implementing and spec'ing `@sheet` first. They both improve sharing styles with Shadow DOM in different ways - the scoping and API's are different enough that there is room for both. -- GitHub Notification of comment by KurtCattiSchmidt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11509#issuecomment-2794442187 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 April 2025 16:28:03 UTC