Firefox

20497 readers

6 users here now

/c/firefox

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

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

[SOLVED: set dom.image-lazy-loading.root-margin.* to a high value] Problems disabling lazy loading of images (lemm.ee)

submitted 2 years ago* (last edited 2 years ago) by Crul@lemm.ee to c/firefox@lemmy.ml

5 comments fedilink hide all child comments

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

[–] stifle867@programming.dev 4 points 2 years ago (1 children)

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.ee 3 points 2 years ago (1 children)

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 points 2 years ago (1 children)

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.ee 2 points 2 years ago

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

Thanks