I was using 11.0.42 on Firefox 80.0.1 (64-bit) on Windows 10.
Initially I planned to post a separate report about the issue but when I saw this thread about that 11.0.43rc1 fixed a corruption issue related to non HTML/HTML content I realized that 11.0.43rc1 could be relevant as I was trying to view .jpeg and .png files. I installed 11.0.43rc1 which fixed the issue. For the record, below here's the thing I had written up but then had not posted as the issue seemed to be covered by the 11.0.43rc1 fix.
----------
subject: Local images are displayed as text/garbage when the file: site is trusted
I'm running NoScript 11.0.42 on Firefox 80.0.1 (64-bit) on Windows 10.
For the past week or two local image files (jpeg, jpg, and png) are displaying as text when I try to view them directly.
For example, if I download
https://noscript.net/noscript/logo.png to c:\tmp and then bring up file://C:/tmp/logo.png in Firefox then it shows a black and white "text" page that starts out with "?PNG ? IHDR??..." (some characters were replaced with ? to get through the forum's anti-spam filter) Right click and view page info shows the type is image/png.
If I create a small file://c:/tmp/logo.htm file containing just <img src=logo.png> then it works fine and I see the logo. If from that page I right click on the image and select view-image then I see the page of garbage text.
I tracked this down and it's caused by NoScript. If I disable all extensions except NoScript then I see garbage text instead of the image. If I disable NoScript then I see the image.
NoScript says that the file://C:/tmp/logo.png page is "safe" as it's the file: "site."
If I make the file: site "default" or "untrusted" then local images display fine.
If I temporarily trust the file: site then I get the page of garbage/text when I hit refresh.
----------
As I'm now running 11.0.43rc1 I can't reproduce the above though if needed I could revert back to 11.0.42 if you want me to try something. At that point I would assume we are dealing with something other than what 43rc1 was intended to fix and so I suspect I should start a new forum thread rather than hijacking this one.
I was using 11.0.42 on Firefox 80.0.1 (64-bit) on Windows 10.
Initially I planned to post a separate report about the issue but when I saw this thread about that 11.0.43rc1 fixed a corruption issue related to non HTML/HTML content I realized that 11.0.43rc1 could be relevant as I was trying to view .jpeg and .png files. I installed 11.0.43rc1 which fixed the issue. For the record, below here's the thing I had written up but then had not posted as the issue seemed to be covered by the 11.0.43rc1 fix.
----------
subject: Local images are displayed as text/garbage when the file: site is trusted
I'm running NoScript 11.0.42 on Firefox 80.0.1 (64-bit) on Windows 10.
For the past week or two local image files (jpeg, jpg, and png) are displaying as text when I try to view them directly.
For example, if I download https://noscript.net/noscript/logo.png to c:\tmp and then bring up file://C:/tmp/logo.png in Firefox then it shows a black and white "text" page that starts out with "?PNG ? IHDR??..." (some characters were replaced with ? to get through the forum's anti-spam filter) Right click and view page info shows the type is image/png.
If I create a small file://c:/tmp/logo.htm file containing just <img src=logo.png> then it works fine and I see the logo. If from that page I right click on the image and select view-image then I see the page of garbage text.
I tracked this down and it's caused by NoScript. If I disable all extensions except NoScript then I see garbage text instead of the image. If I disable NoScript then I see the image.
NoScript says that the file://C:/tmp/logo.png page is "safe" as it's the file: "site."
If I make the file: site "default" or "untrusted" then local images display fine.
If I temporarily trust the file: site then I get the page of garbage/text when I hit refresh.
----------
As I'm now running 11.0.43rc1 I can't reproduce the above though if needed I could revert back to 11.0.42 if you want me to try something. At that point I would assume we are dealing with something other than what 43rc1 was intended to fix and so I suspect I should start a new forum thread rather than hijacking this one.