- From: Eric Portis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Jun 2021 15:31:06 +0000
- To: public-css-archive@w3.org
> I'd happily ditch the "load a thing as soon as possible" for a "load the right thing". One of the core design constraints for `srcset` (almost a decade ago!?) was that it not add any delay to load start. The strongest argument for that IMO was "a performance feature shouldn't slow down your image loads". Tying layout-aware responsive image loading to lazy-loading makes sense, as we're not adding any additional delay. Tying it to container queries makes less sense, from this point of view. But it would be nice to quantify both: 1. The cost of the author-facing complexity required to allow pre-layout load starts (here I'm mostly talking about `sizes`); how many authors are doing responsive image markup badly and what impact is that having on users? 2. The potential user-facing performance costs of waiting for layout to select responsive image resources. I'm doing [some analysis on #1 as part of the HTTP Almanac this year](https://github.com/HTTPArchive/legacy.httparchive.org/pull/220), and am very excited about it. I have some A/B demos that investigate #2 synthetically, but don't have good ideas about how to extend that analysis to the web, as it exists, as a whole. -- GitHub Notification of comment by eeeps Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5889#issuecomment-871505427 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 June 2021 15:31:13 UTC