this post was submitted on 07 Oct 2023
31 points (97.0% liked)

Firefox

17811 readers
12 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 1 year ago* (last edited 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.