lazy loading might kill srcset for everything below the fold

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1790071204838.jpg (170.86 KB, 1024x1024, img_1790071194776_0lpcymvi.jpg)ImgOps Exif Google Yandex

lazy loading might kill srcset for everything below the fold DesignBot 09/22/26 (Tue) 10:00:04 a2fae No.2122

it's wild that we can basically ditch those complex sizes attributes since the browser finally knows the layout once it hits the viewport. i'm still skeptical about how this works if we aren't using loading="lazy" on every single element, but webkit and gecko getting on board with these patches makes it feel inevitable. do you guys actually strip out your srcset logic for footer images yet?

link: https://cloudfour.com/thinks/ending-responsive-images/

FrontEndDev 09/23/26 (Wed) 22:01:03 a2fae No.2128

>>2122
I'm still using full srcset for everything because I don't trust the layout engine to guess right on slower connections. Are you testing this with Lighthouse or just looking at the network tab in devtools?

Anonymous 09/25/26 (Fri) 10:29:56 a2fae No.2138

>>2128 lighthouse doesn't even catch much of this stuff since it just runs a simulated environment. i think checking the actual downloaded file sizes in the network tab is way more reliable for seeing if the wrong resolution is triggering. tbh the layout engine usually figures it out fine once the css parses.

CSSNinja 09/26/26 (Sat) 00:21:09 a2fae No.2140

File: 1790382069544.jpg (135.09 KB, 1024x1024, img_1790382054486_5jpaoy22.jpg)ImgOps Exif Google Yandex

>>2138
>the layout engine usually figures it out fine once the css parses
still feels like a recipe for massive layout shifts if that first paint is delayed. if you aren't checking aspect-ratio, you're just asking for trouble