Google Chrome à l’appui de chargement différé par défaut, à partir de versio…

Google Chrome to support lazy loading by default, starting with version 75

Avant d’acheter un smartphone pliable, il faut toujours regarder les différents appareils disponibles sur le marché. Lequel, permettra vraiment de lire les news chaque jours de manière gréable ?

Google Chrome à l’appui de chargement différé par défaut, depuis la version 75

View Reddit by fernandocole

10 réflexions au sujet de “Google Chrome à l’appui de chargement différé par défaut, à partir de versio…”

  1. [Android Police](


    > The feature works just as you would expect it to work. Images and iframes below the fold of a page will only be loaded if the user scrolls near them, with the exact moment of the load-in depending on factors such as the speed of the network. Most of the time, images and iframes should be loaded ahead of time and users shouldn’t even notice the underlying mechanisms.



  2. As a webdev, hallelujah. Lazysizes does the trick but having this functionality without having to push more JS to users is amazing. I hear Firefox has this in the works, as well.

  3. Will I be able to disable this? It sounds cool, but it also sounds like it depends on a fast Internet connection. Mine is about 500kb/s so I don’t think this will work very well for me.

  4. Can we also make specifying img width and height required too? Less page-jumping would be nice.

    I know a lot of it, maybe most, is because of dynamic insertions. But still.

  5. Can we have the opposite to lazy loading please? I.e. I want websites to at least create placeholders for images and other graphical content immediately before then giving the content a chance to load. How many times have you been halfway through loading a page, go e to click a link or other object only for it to suddenly move down the page as the graphical content is loaded in?

Les commentaires sont fermés.