sanitation@lemmy.today to me_irl@lemmy.world · 2 months agome_irllemmy.todayimagemessage-square19linkfedilinkarrow-up1574arrow-down115
arrow-up1559arrow-down1imageme_irllemmy.todaysanitation@lemmy.today to me_irl@lemmy.world · 2 months agomessage-square19linkfedilink
minus-squareraman_klogius@ani.sociallinkfedilinkEnglisharrow-up7·2 months agoThis is why I wish there’s a way to have lag compensation in UI, as in click on what was there 100ms ago
minus-squareDultas@lemmy.worldlinkfedilinkarrow-up20·2 months agoThey could just load the whole page at once like the old days. But modern web UIs load tons of stuff in the background and then render them after the initial page causing pop in.
minus-squaregrue@lemmy.worldlinkfedilinkarrow-up6·2 months agoIf they weren’t trying to reference tons of JavaScript to do shit like that, they wouldn’t need the goddamned lazy loading in the first place!
minus-squareAlphaOmega@lemmy.worldlinkfedilinkEnglisharrow-up1·2 months agoA good web developer will structure the page to not have “layout shift”. This is either poor design or intentional.
This is why I wish there’s a way to have lag compensation in UI, as in click on what was there 100ms ago
They could just load the whole page at once like the old days. But modern web UIs load tons of stuff in the background and then render them after the initial page causing pop in.
If they weren’t trying to reference tons of JavaScript to do shit like that, they wouldn’t need the goddamned lazy loading in the first place!
NoScript FTW!
A good web developer will structure the page to not have “layout shift”. This is either poor design or intentional.