Forcing this change will negatively impact using some websites with scripting disabled.https://noscript.net/getit/#devel wrote:v 11.4.35rc2
============================================================
[...]
x Forcibly neutralize lazy loading attributes when scripting
is 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?