Page 1 of 1

[Done] Please make neutralizing lazy loading optional

Posted: Fri Aug 23, 2024 8:42 pm
by barbaz
Was about to update NoScript to 11.4.35rc2, but decided not to upon seeing this -
https://noscript.net/getit/#devel wrote:v 11.4.35rc2
============================================================
[...]
x Forcibly neutralize lazy loading attributes when scripting
is disabled
Forcing this change will negatively impact using some websites with scripting disabled.

I have a user script to perform image lazy loading on script-disabled sites (some of which might otherwise not show images at all). When that script malfunctions in a way that results in loading all images at once, websites that expect images to be lazy loaded tend to become really, really slow.

The privacy concern about tracking approximate scroll position did occur to me when writing that user script, but ultimately didn't seem worth me caring about. And the performance gains from lazy loading are significant.

NoScript is a security tool, not a privacy tool. While it seems reasonable enough to default to eager loading on script-disabled pages, I have no idea what could be the rationale for forcing this change on all NoScript users? Is there a security benefit to forcing eager loading that I'm missing?

Could the neutralizing of lazy loading please be made optional?

Re: Please make neutralizing lazy loading optional

Posted: Sat Aug 24, 2024 9:34 am
by Giorgio Maone
barbaz wrote: Fri Aug 23, 2024 8:42 pm Could the neutralizing of lazy loading please be made optional?
v 11.4.35rc3
============================================================
x Gracefully handle new capabilities still unknown to the
settings host (e.g. Tor/Mullvad browser), if any
x Configurable "lazy_load" capability (see
https://github.com/whatwg/html/issues/5250)
x [L10n] Updated fr

Re: Please make neutralizing lazy loading optional

Posted: Sat Aug 24, 2024 3:36 pm
by barbaz
Nice, thank you Giorgio! 8-)

Does the "lazy load" capability apply to the document URL (like "unrestricted CSS" does)? Or does it apply to destination URL of the lazy-loaded resource?

Re: Please make neutralizing lazy loading optional

Posted: Sat Aug 24, 2024 5:59 pm
by Giorgio Maone
barbaz wrote: Sat Aug 24, 2024 3:36 pm Does the "lazy load" capability apply to the document URL (like "unrestricted CSS" does)?
The former: it's a capability of the document triggering the load.

Re: Please make neutralizing lazy loading optional

Posted: Sat Aug 24, 2024 6:19 pm
by barbaz
Giorgio Maone wrote: Sat Aug 24, 2024 5:59 pm
barbaz wrote: Sat Aug 24, 2024 3:36 pm Does the "lazy load" capability apply to the document URL (like "unrestricted CSS" does)?
The former: it's a capability of the document triggering the load.
Awesome Image Added to the sticky.