- From: Matt Wilcox via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 Jun 2021 22:40:26 +0000
- To: public-css-archive@w3.org
Fwiw I don't think the use case of "request an asset as fast as possible" is anything like as important as "load the right asset and avoid wasting potentially hundreds of Kb of inappropriate image data". The part of the feature that allows for early http requests is far less impactful for any page of a realistic size than getting the more appropriate asset for the context in use. Given that the majority of the time "saved" by this behaviour is actually dns lookup time and/or connection establishment... those are mostly redundant? A huge portion of images are going to be on the same domain or a CDN that don't incur an extra lookup, or over http2/3 which don't suffer the same connection overhead. Unless I'm missing something? I'd happily ditch the "load a thing as soon as possible" for a "load the right thing". -- GitHub Notification of comment by MattWilcox Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5889#issuecomment-869233695 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 27 June 2021 22:40:28 UTC