Lofesa commented on issue #1663: Chrome's Native Lazy Loading URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1663#issuecomment-532213259 > > > the distance on where the images are pre-loaded changes with the type of connection, for a 2G connection the distance is bigger than for a 4G, so maybe we interfere with these feature. > > How would we interfere with that feature if we integrated the Chrome lazyloading technique when applicable? I don´t know, cause I have not read the code of the lazyload filter in deep and don´t know what it do step by step. Perhaps an approach can be set `loading = lazy` in all images until pagespeed can determine if the image is in the viewport and when pagespeed can, change it to `loading = eager` or only put the `loading = lazy` attribute when pagespeed put data-pagespeed-lazy-src attribute. The hard thing is determine if the browser is lazyloader capable, I don´t know other method than javascript. Can c++ do a capability test online? or we need a whitelist of brorser versions? At the moment all this stuff is very confusing cause chrome 76 can lazyload images and iframes, but is not enabled by default, the user need to enable it manually.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
