- From: Westbrook Johnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Feb 2023 00:53:55 +0000
- To: public-css-archive@w3.org
For a CSS only usage, I'd say leaning into something like `<link rel=stylesheet href="style.css#sheet">` would be one path, though more invasive. This allows the download of all of the CSS that might be needed for an experience in one request without leaving a bunch of unused CSS attached to the page (performance hit) until you need it. Even if the "need it" doesn't come till the loading of a subsequent page, you'll now have a faster load time as the file is cached from the previous request. @calebdwilliams also hits this on the head for the benefits it brings to declarative shadow DOM. Having a path for a file with multiple `@sheet`s to be including once and then the declarative shadow roots to be able to take parts of that would be a great benefit to that process. This likely requires a little more invasion as it would benefit from something along the lines of https://github.com/WICG/webcomponents/issues/939 as well as ensuring that all CSSStylesSheets were "constructible stylesheets". Each of these could then be addressed later (regardless of their initial acquisition) while also allowing for the form of sub-querying that `@sheet`s would open up a lot of options around how these styles could be used. -- GitHub Notification of comment by Westbrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5629#issuecomment-1411276814 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 February 2023 00:53:57 UTC