- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 31 Jan 2023 17:57:27 +0000
- To: public-css-archive@w3.org
As mentioned above, I think it's pretty important that a feature this invasive has a CSS use apart from any JS. On the surface, I like the idea of allowing `@import`/link to access fragments of a larger css file – but I'm curious what the use-case is for that. My immediate guess would be _performance optimization_, but I'm not actually sure it helps there? Now we're loading a large file, when we only want access to one part of it. But maybe it helps cut down on parse/render time? Is there some other story for how this helps CSS authors write more modular CSS, without relying on JS for the feature to do anything? -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5629#issuecomment-1410825555 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 31 January 2023 17:57:30 UTC