On 16/01/20 19:29, Gerry Hickman wrote:
Dirk Fieldhouse wrote:
You need the 'Classic' version 5.1.9, not the 'Quantum' version that
only works with newer vandalised FF versions.
Thanks,
I installed NoScript classic XPI
then added these two config entries
noscript.surrogate.ibm.replacement
for (let ii of document.querySelectorAll("img[data-src]")){
ii.setAttribute("src", ii.getAttribute("data-src")); }
noscript.surrogate.ibm.sources
!@https://developer.ibm.com/tutorials/l-virtual-filesystem-switch/*
and the page worked correctly straight away!
You are now a NoScript guru!
As you can see, you can either run it with all JS blocked and
selectively enable certain domains (preferred but sometimes hard work),
or trust all JS, or all JS from the visited domain, but rely on its
other features (including blacklisting domains) to sanitise sites that
you visit.
In case anyone would like the scriptlet translated into English, it says
this: for each <img> element in the page that has a 'data-src'
attribute, set the value of its 'src' attribute to the value of its
'data-src' attribute.
By the magic of modifying the page through the Document Object Model
interface in this way, the browser updates the modified elements and the
hidden images appear. This is just what the site JS should do, but in
some code that runs asynchronously from the page load so that the page
appears more quickly (and the visitor won't care, because the images
that the designers expect not to be in the visible in the browser's
scroll window will have loaded by the time the page has been scrolled
down). But if the mechanism used to make the load asynchronous fails
(maybe using some unsupported JS feature), or if you've disabled JS, the
images fail to appear.
/df
--
London
UK
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
