- From: Justin Fagnani via GitHub <noreply@w3.org>
- Date: Wed, 21 Jan 2026 21:32:10 +0000
- To: public-css-archive@w3.org
@bramus > > I’m wondering if `@export` would be a name more consistent with the rest of the web platform. I was confused when I first saw `@sheet`, but at least to those who write JS, `export` is a familiar concept. We already have `@import`, so this would be nicely analogous. > > Everything in a style sheet get exported by default, so all contents of all style sheets – using `@sheet` or not – are implicitly wrapped in a (non-existent) `@export`, no? Right now _nothing_ is exported from a style sheet to JS except for the sheet itself in the default export. `@sheet` as proposed would be the first thing to create a named export. I have been concerned about needing to know which things create named exports as that set expands in the future. How would we export class name, and would that use something like `@export` or a new at-rule for declaring a class name or selector, and that new rule creates a named export? -- GitHub Notification of comment by justinfagnani Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5629#issuecomment-3781260337 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 January 2026 21:32:11 UTC