- From: Oliver Williams via GitHub <sysbot+gh@w3.org>
- Date: Sun, 24 Mar 2024 11:15:19 +0000
- To: public-css-archive@w3.org
> With this in mind, I wonder if the use of @export would be more confusing as it is not reciprocal to the @import token that is already available in CSS? 100% agree - I would naturally assume I could `@import` something I have `@export`ed, although from the CSSWG meeting transcript it looks like you will be able to to do this so maybe the export name is ok (although I've not seen anyone answer Miriam's question about whether being able to `@import` an `@export` is even a useful thing to be able to do, whereas the JavaScript use case is very compelling by itself). Because the thing getting exported is a `CSSStyleSheet` I find the `@sheet` syntax more clear regardless. > `@export @sheet` This syntax is ugly imo. Particularly if you are using other `@rules` like `@layer` within the sheet, its too many `@`s that it feels a bit overwhelming. It would be unfortunate to adopt an unnecessarily verbose syntax just for the purposes of catering to a totally speculative potential (and imo questionable) future CSS feature. -- GitHub Notification of comment by o-t-w Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5629#issuecomment-2016774861 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 24 March 2024 11:15:21 UTC