file:/// - NoScript 2.9.5.1 "Blocks" Local Files, like .MHT

[rschneider]

NOTE: This bug report has a VERY SPECIFIC COMMONALITY with "file:/// bookmarks... now blocked" by DavePlatt, Thu Nov 24, 2016 - but ALSO UNIQUE DIFFERENCES IN THE WAY IT EXHIBITS A SYMPTOM - therefore I am posting this as a separate Topic. IT SHOULD BE NOTED THAT THE COMMON ELEMENT "file:///" MAY HELP ARRIVE AT THE CAUSE, AND THEREFORE SOLUTION - - - so DavePlatt's, and my bug report, should be taken as 2 examples that probably derive from a common regression bug in NoScript. I amended my topic's title by adding the prefix "file:///" to help direct all readers to this commonality of symptom - and quite possibly cause - of the bug. Very detailed troubleshooting steps are included below.

NoScript and UnMHT (last updated to v8.2.0 on Jul 17, 2016) have co-existed peacefully in Firefox for more than 10 years. Immediately upon NoScript's update to v2.9.5.1, NO .MHT-saved webpages display in Firefox - BUT ONLY IF NOSCRIPT IS ENABLED.

* ALL webpages saved with UnMHT in Firefox DO display in Internet Explorer.

* When NoScript is "DISABLED" (dangerous for security) and Firefox is restarted, .MHT-saved webpages display again in Firefox.

* When NoScript is again "ENABLED" and Firefox is restarted, NO .MHT-saved webpages display. The saved .MHT webpage is totally blank, tab title is blank, and there is no tab favicon. And when the blank/non-displayed page is right-clicked, no context menu even pops up.

* SAVED .MHT WEBPAGES ALL DISPLAY the URI PREFIX "file:///" in the web browser address bar - since this is a local disk file being displayed. Hence, the commonality to mine and DavePlatt's bug report as mentioned in the first paragraph above.

* NOTE: A webpage opened in Internet Explorer, and SAVED AS a .MHT by IE, ALSO WILL NOT DISPLAY in Firefox, if NoScript is enabled (but does, of course, display properly in IE when the saved .MHT file is right-clicked and "Open with Internet Explorer" is selected).

* ALL .MHT files - whether Internet Explorer pages saved with IE, or Firefox webpages saved with the UnMHT extension - display in IE.

* NO .MHT files - whether Internet Explorer pages saved with IE, or Firefox webpages saved with the UnMHT extension - display in Firefox with the newest versions of NoScript ENABLED (see below for versions tried that are affected).

Bearing in mind all the foregoing, the problem is that NoScript's update to v2.9.5.1 contains a regression bug - a failure to display local files (file:///), exemplified by those saved from any browser in .MHT file-format (something that was NOT a problem during the last several years of NoScript's Full Stable Releases). This is NEW, and UNACCEPTABLE.

I use .MHT files constantly - even making my own .MHT files from scratch - to display technical presentations. NoScript MUST be restored to functionality, regarding display of any local disk files, not just those in .MHT format. (This applies not only to the now-blocked .MHT files of most interest to me, but to ALL local disk files having the "file:///" URI prefix, and opened in a web browser with NoScript installed.

The following NoScript Options WHITELIST entries exist in my installation: "file", "file:", "file://", unmht://unmht", "unmht://undefined", "unmht://undefinedundefined". When I try to add "file:///" to NoScript's whitelist (the URI prefix that displays in an address bar of an opened .MHT or other local file), the NoScript "Allow" button is grayed-out and inactive - NoScript will not allow whitelisting the URI prefix that MIGHT correct this regression bug.

* I TRIED BUILD v2.9.5.1rc1 - THE .MHT PROBLEM EXISTED - No local disk saved .MHT files would display (whether saved from Internet Explorer, or Firefox with the UnMHT extension).

* I REMOVED NoScript v2.9,5.1rc1, then restarted Firefox.

* I INSTALLED AN OLDER VERSION (previous to the problem update v2.9.5.1) from the AMO NoScript listing of previous versions (v2.9.5rc36), and Restarted Firefox - THE PROBLEM STILL EXISTED.

* I THEN INSTALLED THE PREVIOUS FULL STABLE RELEASE THAT I WAS RUNNING BEFORE THE PROBLEM UPDATE TO v2.9.5.1 (which was v2.9.0.14, Released August 8, 2016) - FINALLY, WITH OLD VERSION 2.9.0.14, local-stored .MHT files ALL DISPLAY AGAIN !!!

That is to say, the "file:///"-blocking that now infests NoScript never existed before Aug 8, 2016 - BUT IS NOW THERE. Remember, I've been using NoScript and UnMHT to save, and read in Firefox, .MHT files without any problems for over 10 years - until the update from stable v2.9.0.14 to v2.9.5.1 just a few days ago. The problem also existed in 2 previous release candidates I tried between the 2 stable releases, so exactly when the regression crept in isn't known to me. But DavePlatt and I were both hit with it when NoScript updated to 2.9.5.1. Other reviewers on NoScript's AMO page mention blocked/blank pages for the "Stylish CSS editor", "about:memory", "about:support" pages, etc.

* I TURNED OFF AUTO-UPDATING for NoScript, Exported my Noscript settings, and plan to live with the old version until NoScript solves the .MHT local file-blocking regression bug. I've not had this serious a problem with a Firefox extension in years.

[It's amazing how many - dozens - of rc# versions/betas were introduced between 2.9.0.14 (2016/08/08) and 2.9.5.1 (2016/11/21); and I have no inclination to find out where this .MHT-blocking regression bug first crept in. That's not my job. But this regression bug DOES EXIST IN THE 3 MOST RECENT VERSIONS I TRIED - and MUST be found and removed. My suggestion is you DO NOT ISSUE ANOTHER FULL STABLE RELEASE UNTIL THIS BUG HAS BEEN BANISHED. I no longer have confidence in NoScript, and will keep Automatic Updating turned OFF for NoScript.]

R. Schneider

[barbaz]

@Schwubbeldiwupp Moved your post to the thread about the Stylish bug.

@rschneider Thanks for the detailed report, but I suggest you adjust your attitude if you'd like a solution. Recall that you got NoScript for free, because Giorgio chose to make it free software. As such, neither Giorgio nor NoScript owe you anything.

Demanding that Giorgio fix this problem, as you did here...

This is NEW, and UNACCEPTABLE.

[...]

[It's amazing how many - dozens - of rc# versions/betas were introduced between 2.9.0.14 (2016/08/08) and 2.9.5.1 (2016/11/21); and I have no inclination to find out where this .MHT-blocking regression bug first crept in. That's not my job. But this regression bug DOES EXIST IN THE 3 MOST RECENT VERSIONS I TRIED - and MUST be found and removed.

... and then writing stuff like this quote...

My suggestion is you DO NOT ISSUE ANOTHER FULL STABLE RELEASE UNTIL THIS BUG HAS BEEN BANISHED. I no longer have confidence in NoScript,

... makes it look like you're just here to rant, which I assure you will not do you any favors.

[Giorgio Maone]

Please check latest development build 2.9.5.2rc1, thank you.