Page 1 of 1
Noscript not saving any script settings for sites
Posted: Fri Nov 24, 2017 11:22 pm
by Nomad
Hello,
Recently updated to Quantum and Noscript is have serious issues. Every time I allow a script (either Trusted or Temporary) and attempt to reload page, the setting automatically reverts back to the prior Default setting.
Doesn't seem to matter which page I'm at. Any ideas?
Re: Noscript not saving any script settings for sites
Posted: Fri Nov 24, 2017 11:30 pm
by Pansa
Nomad wrote:Hello,
Recently updated to Quantum and Noscript is have serious issues. Every time I allow a script (either Trusted or Temporary) and attempt to reload page, the setting automatically reverts back to the prior Default setting.
Doesn't seem to matter which page I'm at. Any ideas?
Site is probably http, and when changing the setting you chose the "https only" option (green lock) if you want rules to apply to http, you need to choose the red lock (http and https)
If only https is allowed the http website on reload will again be in default (therefore it appears that nothing happened). Actually a https rule was still created (i think).
This at the moment even applies to untrusted, even if there is no lock to see. If you want to block an HTTP site, at the moment you have to choose "trusted" set the redlock and then untrust it.
Re: Noscript not saving any script settings for sites
Posted: Sat Nov 25, 2017 1:30 am
by Noh
Pansa wrote:Nomad wrote:Hello,
Recently updated to Quantum and Noscript is have serious issues. Every time I allow a script (either Trusted or Temporary) and attempt to reload page, the setting automatically reverts back to the prior Default setting.
Doesn't seem to matter which page I'm at. Any ideas?
Site is probably http, and when changing the setting you chose the "https only" option (green lock) if you want rules to apply to http, you need to choose the red lock (http and https)
If only https is allowed the http website on reload will again be in default (therefore it appears that nothing happened). Actually a https rule was still created (i think).
This at the moment even applies to untrusted, even if there is no lock to see. If you want to block an HTTP site, at the moment you have to choose "trusted" set the redlock and then untrust it.
THANK YOU. This was driving me nuts.
That it applies to setting untrusted scripts is annoying but until its changed its not a big deal to just leave them blocked by default.