- From: Justin Fagnani via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Jan 2023 23:19:10 +0000
- To: public-css-archive@w3.org
Great summary @tabatkins ! > When importing a stylesheet using JS imports, while the overall sheet is the default import (how it works today), all the @sheet rules are exposed as separate CSSStyleSheet objects as named exports. I do want to be careful and conservative about this point, since it would be the first introduction of named exports in a stylesheet module. How might it interact with some of the ideas in https://github.com/w3c/csswg-drafts/issues/3714 - that might create named exports for things like class names like userland modules do today. I don't _think_ it's much of a concern, since it might be rare to have top-level rules/exports _and_ bundled stylesheets, and even if you did you might be very unlikely to have name collisions, and even if you did have collisions, you're probably generating a bundle with a tool that can handle that by renaming things. But it's something to consider. -- GitHub Notification of comment by justinfagnani Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5629#issuecomment-1405802717 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 January 2023 23:19:12 UTC