EDIT: Today I dug a bit more and found that dom.image-lazy-loading.enabled preference has been removed and saw this comment on a related thread:

FWIW, it should still be possible to effectively turn off lazy loading by setting dom.image-lazy-loading.root-margin.* to a big number.

Which I tried (value 100000) and it works!

Hi, I have a slow connection and for pages with lot of images it’s very convenient to open the page and wait for all the images to load before watching them.

I have dom.image-lazy-loading.enabled set to false but I have found webs where it doesn’t work, like with Behance galleries. I see the loading="lazy" attribute on the img tags, but they don’t load until I scroll down to them.

Does anyone know if I’m missing something or if there is any way to debug it further?

There are also pages (like this one) in where I don’t see the loading="lazy" attribute but I see a lazy-images.js file on the Debugger file list, data-lazy-src attributes in img elements and other img elements with loading="lazy" inside noscript tags. I understand that the dom.image-lazy-loading.enabled setting may not work with custom lazy loading implementations.

Does anyone know of any solution for these cases?

EDIT: I’ve also tried LazyLoadify add-on with no luck.

Thanks!

  • jsdz@lemmy.ml
    7·
    1 year ago

    Lazy loading of images through the mechanism controlled by that setting is relatively new, and many sites unfortunately still have javascript to do something similar in browsers that don’t support it.

    It’d be nice if Firefox could let us turn off the new feature in a way that’s undetectable without specific measures to look for it, but it seems extremely unlikely that Mozilla will ever find that worth the effort of doing. In some cases you might be able to just block a single script with noscript or ublock, but all the implementations are different and there’s no general solution unless maybe if you find or create an extension specific to that purpose.

  • stifle867@programming.dev
    4·
    1 year ago

    Just a theory as I haven’t looked into this yet. It could be that despite the loading="lazy" behaviour being disabled in the config, the website may be using some kind of polyfill to replicate the behaviour using javascript?

    What happens if you disable javascript and test both pages? (javascript.enabled=false, ublock, noscript, etc)

    • Crul@lemm.eeOP
      3·
      1 year ago

      the website may be using some kind of polyfill to replicate the behaviour using javascript?

      Yeah, that’s what I meant with “I understand that the dom.image-lazy-loading.enabled setting may not work with custom lazy loading implementations.” and asked for different solutions.

      What happens if you disable javascript and test both pages?

      Good idea! It works with the 2nd one, but Behance doesn’t even load without JS.

      Thanks for the help!

      • stifle867@programming.dev
        4·
        1 year ago

        What you can do now is use either ublock or noscript to narrow down exactly which javascript files are doing the lazy loading and selectively blocking just those. That way you may be able to run the javascript required for the page to function and only disable the lazy loading.

        • Crul@lemm.eeOP
          2·
          1 year ago

          It may be worth for the most visited pages (like Behance), but I was hoping to find a more general solution.

          Thanks