PNG pictures not showing

[Quest]

I can't see png -pictures anymore on page

http://ocean.dmi.dk/arctic/meant80n.uk.php

and on another page too.

Is it the new RC4 or only me?

Only wholly disabling Noscript helps.

[Giorgio Maone]

The problem seems to be the site dependining on google-analytics.com to be enabled in order to show its images.
Looks like it's about time to bring Script Surrogates back...

[therube]

I'm not seeing that, the need for google-analytics.com?

Current year displays, without anything.
If you want to switch to a different year, only dmi.dk is needed?



I will note, that after allowing dmi.dk, the icon changes to an expected icon, showing, I guess it is that only some of the domains are allowed.

Though if you then click a different year, while the graph does change as expected, the icon now shows a question mark, which is horribly confusing to me?

[therube]

Cry.

New Profile
NoScript

nothing allowed, graph shows
click 2017, no change in graph reflected

allow dmi.dk
page refreshes, graph shows
click 2017

icon becomes question mark
google-analytics.com turns up in both red & black
page displays (though I'm unable to copy it - for whatever reason???), "The image "...1971.png" cannot display because it contains errors."

allow black google-analytics.com
page refreshes
same "image error"

allow red google-analytics.com
page refreshes
same "image error"
no other domains to allow

refresh the page
force refresh the page
same "image error"

revoke

image displays

allow all this tab
page works as expected
though icon still shows as question mark


oddly 2016 will display its graph with only dmi.dk allowed (& nothing else)


appears, the only way to get things to work correctly, is to allow all this tab?
as in allow, dmi.dk, then allow both google-analytics.com does not allow the page to work.
(seem to recall running into similar before?)

[therube]

(Wonder what might have broken or is broken in my original Profile?
Having Prefs in a black box is a great benefit .
Cry again.

grep -i noscript prefs1.js > 1
grep -i noscript prefs2.js > 2
compare 1 2
but nooooo!)

[therube]

(seem to recall running into similar before?)

That was here, https://forums.informaction.com/viewtop ... =7&t=24739:

Allow & Temp-Allow do not allow ( ) typing into the Reply box, nor does the reply box display its editing controls (as pictured above).

The only way I see to get things allowed, is to 'Set all on this page to Temporarily TRUSTED'.
(Not even Allow Globally works.)

Though in the case here, both Allow Globally & Temporarily Allow All This Page work.

[Quest]

I have not tested this more, but:
- The page worked before RC4, I even tried different profile that was not NS updated and it worked.
- Other years don't work either, but the link on the right "See the annual mean +80N anomaly here" works and shows a png-picture.
- Completely different page https://seaice.uni-bremen.de/sea-ice-concentration/ don't work either; the picture shows, but if you click it to enlarge, it don't.
- NS is the only extension I have. Pages work if I disable NS (from FF settings or Globally from NS) but not if I temporary trust the page.
- I have custom allowed (only) scripts on https:google analytics.

I still think the reason is somewhere in NS ...RC4?

[Giorgio Maone]

I have not tested this more, but:
- The page worked before RC4, I even tried different profile that was not NS updated and it worked.
[...]
I still think the reason is somewhere in NS ...RC4?

Does it work back for you with RC3?

[therube]

Does it work back for you with RC3?

dmi.dk works with RC3 without the need to allow google-analyitics.
(Unless something broke again?)

Completely different page https://seaice.uni-bremen.de/sea-ice-concentration/ don't work either; the picture shows, but if you click it to enlarge, it don't.

I'm not seeing any failure there?
I'm not sure why NoScript would be having any affect there?
From what I see, clicking a picture there, simply opens the picture (.png as it is) in the current tab.

Click a picture, opens the image directly.
Clicking that image, toggles from fit-to-page to full-size.

[therube]

dmi.dk works with RC3 without the need to allow google-analytics.
(Unless something broke again?)

That may very well be the case.
I am now seeing different behavior after having put RC4 back in.

IOW, I bet if I start with a new Profile, & install RC3, that google-analytics will be required.
And then maybe something like if I then put in RC4, then revert back to RC3, all in the same profile, GA will no longer be needed.


No time to look further, at present.

[Giorgio Maone]

Does it work back for you with RC3?

dmi.dk works with RC3 without the need to allow google-analyitics.

I think I understand what's going on... trying to fix it in RC5.

[Giorgio Maone]

Please check latest development build, thanks.
v 10.1.8.3rc5
=============================================================
x Fixed dynamic script injection regression breaking images
loaded as frame content (thanks Quest for report)
+ Included license files in the XPI

[therube]

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?

[therube]

new profile
install 3
load http://ocean.dmi.dk/arctic/meant80n.uk.php
icon looks OK
graphs do not change
allow dmi.dk
icon looks OK, allowed with other blocking
graphs work
icon displays with a question mark

---

new profile
install 4
load http://ocean.dmi.dk/arctic/meant80n.uk.php
icon looks OK
graphs do not change
allow dmi.dk
icon looks OK, allowed with other blocking
graphs do not work
the image ... cannot be displayed because it contains errors
note the the back-arrow did record graph-year click-history
icon displays with a question mark
allow black google
graphs do not work
allow red google
graphs do not work
allow globally
graphs work
icon displays with a question mark

---

new profile
install 6
load http://ocean.dmi.dk/arctic/meant80n.uk.php
icon looks OK
graphs do not change
allow dmi.dk
icon looks OK, allowed with other blocking
graphs work
icon displays with a question mark

---

so, 3 & 6 behave the same, graph works without specifically needing to allow google*
4 required google*, or more accurately, needed Allow Globally or Allow All This Page for it to work

[Quest]

I don't see anything wrong anymore. On the dmi site I have only http:ocean ... custom-allowed script and frame (as before). Everything from Google is defaul (with no checks). The other sites that had this problem seem to be working OK now.