Native lazy loading has landed in Chrome

Post by davidweatherall » Mon, Aug 26, 2019, 12:11 PM UTC

cameronbrown wrote: post #8

sharpercoder wrote: post #5

As a developer and systems architect, I really like this. As uset, I hate this so much. On slower connections, I like to load a page, swap tabs, come back later and expect the page to be loaded. This mechanism will now break (and is already brokrn by the usr of these lazy loading libs).

Hmm, maybe if websites don't use lazy loading JavaScript anymore (guilty as charged btw) then you'll be able to configure it however you want in browser settings?

Post by tsp » Mon, Aug 26, 2019, 12:18 PM UTC

Post by [deleted] » Mon, Aug 26, 2019, 12:26 PM UTC

sharpercoder wrote: post #5

As a developer and systems architect, I really like this. As uset, I hate this so much. On slower connections, I like to load a page, swap tabs, come back later and expect the page to be loaded. This mechanism will now break (and is already brokrn by the usr of these lazy loading libs).

Post by mantas » Mon, Aug 26, 2019, 12:42 PM UTC

davidweatherall wrote: post #11

cameronbrown wrote: post #8

Earlier quoted context omitted.

Hmm, maybe if websites don't use lazy loading JavaScript anymore (guilty as charged btw) then you'll be able to configure it however you want in browser settings?

I imagine anti-lazyloading extensions will start appearing soon.

Post by Raphmedia » Mon, Aug 26, 2019, 1:30 PM UTC

mark_and_sweep wrote: post #14

danShumway wrote: post #12

Earlier quoted context omitted.

I'm missing why this is a bad thing? It make polyfills way easier, and makes it drop-dead simple to programmatically toggle lazy-loading on existing elements.

I think the previous poster was referring to the unnecessary `=== true` part.