- From: Westbrook Johnson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Feb 2024 18:14:33 +0000
- To: public-css-archive@w3.org
> From an architectural pov, I would be wary of introducing features in the web platform to do things that are seen as similar but slightly different, as that tends to cause confusion and poor DX.
This is a worthwhile line of investigation, and would likely benefit from actual user testing or surveying, etc. Historically, we've done `import`/`export` within the JS context, but neither CSS nor HTML have done this bi-directionally, even in their own context, to the best of my understanding. As we expand the use of Import Attributes, it'll be good to take a stance on whether that should be more like something that exists or more clearly a new feature. That hopefully means that an answer here could be applied to the conversation around `with { type: 'html' }`, too.
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?
--
GitHub Notification of comment by Westbrook
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5629#issuecomment-1964819859 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 February 2024 18:14:34 UTC