6 ms·
It is the web developers choice to decide whether or not to deal with bad/poor internet connections. Most do not. Lazy loading makes it impossible to do anythi
by tekla 3y ago
It is the web developers choice to decide whether or not to deal with bad/poor internet connections. Most do not.
Lazy loading makes it impossible to do anything to manage a poor connection.
- tentacleuno 3y agoSeems hard not to these days, especially with service workers which can cache resources for offline use.
- syndicatedjelly 3y ago> Lazy loading makes it impossible to do anything to manage a poor connection. This was the exact problem lazy loading was supposed to solve
- hunter2_ 3y agoIf the problem was out-of-viewport images impeding the receipt of assets that do affect the viewport (CSS, fonts, etc.) then it would be good to postpone fetching those images just until everything else is received, rather than postponing until they're closer to the viewport.
- syndicatedjelly 3y agoFun fact, if you type your password, it will show up as ***
- plorkyeran 3y agoWhich is indeed why it's a terrible idea.
- ponderings 3y agoMakes me wonder what other great ideas we've implemented.
- vhcr 3y agoIn this case it's also the choice of the user, they could choose to ignore the lazy loading tags (I know OP mentions their browser doesn't supports it, but they could choose another browser)
- xyzzy3000 3y ago"Best viewed in Internet Explorer" is absolutely not something that needs to make a comeback.