- From: Austin Hammer via GitHub <noreply@w3.org>
- Date: Wed, 18 Feb 2026 19:27:29 +0000
- To: public-css-archive@w3.org
> @austinh I think at least the second one is kinda unsolvable? Or what am I missing? You do need to do layout to determine which image to load, so by definition you can't load the image eagerly, right? You could prefetch or something, I guess, but... I guess Im asking if there is any suggested solution to "right size" images for hero or even just initial viewport images - but say you don't know the size upfront because it's expressed in container query. Sizes=auto always requires a lazy load. Is lazy really the soonest the browser can load this information? I saw a proposal at some point for after-layout - something in between eager and lazy. This would allow for better quality images but also better performance (not over fetching for example). -- GitHub Notification of comment by austinh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5889#issuecomment-3922741764 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 February 2026 19:27:29 UTC