Slashdot Mirror

← Back to Stories (view on slashdot.org)

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

Posted by msmash on from the up-next dept.

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.

1 of 57 comments (clear)

  1. Don't DL anything until the user scrolls to it by tepples · · Score: 4, Informative

    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).