Built-in Lazy Loading Lands in Google Chrome Canary (bleepingcomputer.com)

secwatcher writes: Google has started rolling out support for built-in lazy loading inside Chrome. Currently, support for image and iframe lazy loading is only available in Chrome Canary, the Chrome version that Google uses to test new features. Two flags are now available in the chrome://flags section of Chrome Canary. They are: chrome://flags/#enable-lazy-image-loading, chrome://flags/#enable-lazy-frame-loading. Enabling these two flags will activate a new type of content loading behavior inside the Chrome browser. The two flags have been available in Chrome Canary for a few days, since v70.0.3521.0.

Comments

Lazy loading is what?

[Anonymous Coward]

Tells us the exact names of the config flags, doesn't even explain what lazy loading is. More like lazy editing.

Don't DL anything until the user scrolls to it

[tepples]

In the web platform, lazy loading means don't download anything until the user scrolls to it.

A lot of websites have implemented their own lazy loading in JavaScript for two reasons. One is improving perceived page load time by prioritizing the first screenful of the document. The other is saving server bandwidth (and client bandwidth for users on metered cellular Internet) by not serving large images that the user is not likely to view. But two drawbacks of this sort of lazy loading are 1. incompatibility with clients that do not use JavaScript and 2. incompatibility with clients that download a page over unmetered home Internet for later reading while offline or while on metered cellular Internet (such as while riding the bus).

Re:Don't DL anything until the user scrolls to it

[AvitarX]

Oh, that is the worst!

instead of one time waiting a little longer, not when I scroll it stops every couple of seconds.

I HATE it when sites do that.

Especially if it's a shopping site, I can scroll quite quick deciding what I want to buy or not, and whenever I hit back after adding to cart, the place is lost.

Canary == Nightly

[tepples]

Chrome Canary is the unstable nightly build of the Google Chrome web browser, akin to Firefox Nightly.

Does Lazy Loading break Ctrl + F/"find in page"?

[SB5407]

I'd like to know if the Lazy Loading function of deferring loading images and third-party iframes on the page until the user scrolls near them breaks Ctrl+F/"find in page".

Google had to re-do "Print" and "Save Page As" in order to support Lazy Loading. Did they also make Ctrl+F work or not?

Re:Does Lazy Loading break Ctrl + F/"find in page"

[mrbester]

Unless it is dynamically loaded content Ctrl-F will work just fine as the text of the document has still been fully download, just not necessarily all the images it describes.