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.

2 of 57 comments (clear)

  1. Re:Don't DL anything until the user scrolls to it by AvitarX · · Score: 5, Interesting

    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.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  2. Does Lazy Loading break Ctrl + F/"find in page"? by SB5407 · · Score: 4, Interesting

    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?