Page 1 of 1
NoScript prevents opening MHTML files
Posted: Thu May 29, 2025 11:42 pm
by NoCrap
I have NoScript v13.0.8 running on the Vivaldi browser in Windows 10 x64. I often save web pages of interest as MHTML files. Lately when trying to view these I find that NoScript is preventing it.
I had first noticed some trouble early last month but at that time changing "file:///" in the address bar to "file://" would let the page load. Ctrl-R would sometimes let it load.
NoScript has "file://" set as Trusted and I created a rule making "file:///" be Trusted too but that doesn't fix the problem.
My workaround now is to have MHTML files open in vanilla Chrome instead, where I have no extensions installed. But this is a little clumsy.
--> Is there anything I can set in NoScript Options to allow opening MHTML files?
Thanks
Re: NoScript prevents opening MHTML files
Posted: Fri May 30, 2025 3:24 pm
by barbaz
NoCrap wrote: ↑Thu May 29, 2025 11:42 pm
NoScript has "file://" set as Trusted and I created a rule making "file:///" be Trusted too but that doesn't fix the problem.
Normally this entry should be just "file:" (and the padlock set to red/unlocked). Does changing to that help?
Re: NoScript prevents opening MHTML files
Posted: Fri May 30, 2025 7:00 pm
by NoCrap
I've now added both "file:" and "file:/" as Trusted unlocked permissions, but no joy. Vivaldi still can't open MHTML files that it saved.
Thanks for your help.
Re: NoScript prevents opening MHTML files
Posted: Fri May 30, 2025 7:03 pm
by NoCrap
That's in "Per-Site Permissions" of course. Btw is there a way to remove rules / delete a permission from that listing?
Re: NoScript prevents opening MHTML files
Posted: Sat May 31, 2025 8:06 am
by fatboy
Re: NoScript prevents opening MHTML files
Posted: Sat May 31, 2025 3:38 pm
by NoCrap
Thanks; I see now that to completely delete a permission we just need to set it to the default value. I had tried that but thought that "nothing happened" because it only disappears after a page refresh.
Re: NoScript prevents opening MHTML files
Posted: Sat May 31, 2025 4:33 pm
by NoCrap
Doing some more actual work on my end (!) RESOLVED this...
• As I'd reported, my Vivaldi (which I keep up-to-date) would not open MHTML files; the page would be blank.
• All NoScript Options were at their default values, except for my many Per-Site-Permissions.
• I exported my Per-Site-Permissions to save those.
• I removed NoScript from Vivaldi.
• I re-installed NoScript in Vivaldi.
• Vivaldi would then open MHTML files properly.
• I Imported my Per-Site-Permissions list, restoring NoScript to my current usage.
• Vivaldi continues to open MHTML files correctly, including through an update and a reboot.
SO - there is no fundamental problem; something just got confused.
Re: NoScript prevents opening MHTML files
Posted: Sat May 31, 2025 4:40 pm
by barbaz
(The "RESOLVED" post was posted while I was writing this post, but this post maybe useful information anyway)
I just tried this in Vivaldi 7.4.3684.43 (on Linux) with NoScript 13.0.8, and:
- I don't have any issue opening an MHT file using File > "Open File..." with NoScript in completely default configuration.
- If I go to chrome://extensions/ and set NoScript allowed access to file: URLs, then I get a blank page, but setting "file:" to Trusted gets it working.
- If I customize the Trusted preset in NoScript Options > General, I get the issue you're describing. Reverting the Trusted preset to everything allowed does NOT get it working again.
When the issue occurs, reloading with Ctrl-Shift-R seems to load the MHT file correctly.
F12 Developer tools for the broken page are spammed with messages like
Code: Select all
NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://[ff00::]/chrome-extension://doojmbjmlfjjnbmnoijecmcbfeoakpjm/nscl/c…0039ff2-8d5e-457a-bc43-09e94147440c%3A84860f33-6481-4d65-be1b-5d170644ae91'.
at browser.runtime.sendSyncMessage (chrome-extension://d…ncMessage.js:564:13)
at refetch (chrome-extension://d…/staticNS.js:128:36) "SyncMessage 90039ff2-8d5e-457a-bc43-09e94147440c:84860f33-6481-4d65-be1b-5d170644ae91 error in <redacted file: URL of my MHT file>: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://[ff00::]/chrome-extension://doojmbjmlfjjnbmnoijecmcbfeoakpjm/nscl/c…0039ff2-8d5e-457a-bc43-09e94147440c%3A84860f33-6481-4d65-be1b-5d170644ae91'. (response https://[ff00::]/chrome-extension://doojmbjmlfjjnbmnoijecmcbfeoakpjm/nscl/c…0039ff2-8d5e-457a-bc43-09e94147440c%3A84860f33-6481-4d65-be1b-5d170644ae91 - - )"
Error: SyncMessage Error Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://[ff00::]/chrome-extension://doojmbjmlfjjnbmnoijecmcbfeoakpjm/nscl/c…72e96ce-a7c8-4ebd-a7f1-3277389ba6ab%3A84860f33-6481-4d65-be1b-5d170644ae91'.
at browser.runtime.sendSyncMessage (chrome-extension://d…ncMessage.js:594:20)
at chrome-extension://d…ncMessage.js:610:31
Caused by: NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://[ff00::]/chrome-extension://doojmbjmlfjjnbmnoijecmcbfeoakpjm/nscl/c…72e96ce-a7c8-4ebd-a7f1-3277389ba6ab%3A84860f33-6481-4d65-be1b-5d170644ae91'.
at browser.runtime.sendSyncMessage (chrome-extension://d…ncMessage.js:564:13)
at chrome-extension://d…ncMessage.js:610:31
'SyncMessage immediate retry failed on
<redacted file: URL of my MHT file>