Sigh. Is there a trick question in here? I guess you need to tell us the result we're supposed to be seeing

.
Anyhow...
Does sessionstore.jsonlz4 play into things?
new profile
load
http://ocean.dmi.dk/arctic/meant80n.uk.php
load about:addons -> extensions
install NS3
dmi.dk works only needing to allow dmi.dk
delete all files from profile - except for sessionstore.jsonlz4
start FF
[i have seen the session automatically load, quite unexpectedly
i have had about:sessionrestore load, prompting me to load the prior session, not quite expected either, but OK]
load session from sessionrestore
dmi.dk loads
about:addons -> extensions loads
install NS4
at that point, icon shows as allowed (totally unexpected), dmi.dk simply works (ditto)
the about:addons -> extensions does show NoScript, but the page is broken, displays oddly
so two weird behaviors; dmi.dk was not blocked, addon page did not display properly
refresh both pages
dmi.dk now shows as blocked
about:addons -> extensions displays normally
dmi.dk is now blocked, you cannot change graphs (expected)
about:addons -> extensions, looks normal (expected)
now why did i retain sessionstore.jsonlz4 while deleting all else from the profile?
only so that I would not have to type the two URI being held in sessionstore one again, no other reason.
Anyhow, the result of doing only that, retaining that single file, & restoring its' session data, that alone was enough to alter what happened once you install NoScript.
Point is, at this point, it seems the only way to test, is to start with a completely new Profile, each time, & follow the exact same steps in installing NoScript & testing a particular website. Otherwise, any other actions potentially can only lead to kaos

.
So does a question like "does it work" (much like, "does it hurt" [a good movie IMO]) really have an answer?