Can't allow websites anymore

[myki]

Hi,
It has been severall years now that I use NoScript without any problem, I love it and I want first to thanks its creators...

But now, I don't know what I did, but when I try to allow for example google.fr, the sign remains red and all that I can do is "Allow [https://www.google.Fr]".
Before, the icon becomed white and the site was allowed to load...

I tried to uninstall / reinstall noscript, but it had no effect (maybe settings were kept somewhere ??).

Thanks for your precious help !

[anna]

I second this, it started very recently, sometime during the last month.

My Firefox version is 50.0.2, sites on which this occurs have all relevant domains allowed, however the NoScript 'blocked' notification and site-specific "Enable Javascript" warning still appear.
NoScript context menu shows "Allow <full address>" and "Temporary allow <full address>" but nothing changes when they are clicked.

Disabling and uninstalling the addon doesn't help, only resetting Firefox completely, after which the issue can still be reproduced perfectly just by installing NoScript.

It seems like some setting cannot be controlled from the addon's UI and remains after the addon is removed.

Any suggestion would be appreciated!

[barbaz]

Do you have Scripts Globally Allowed?
Are you visiting sites you've Marked as Untrusted?

viewtopic.php?p=85568#p85568
viewtopic.php?p=85582#p85582

[anna]

I have Scripts Globally Allowed, and some of the problematic sites weren't ever Marked as Untrusted

[barbaz]

Er, anna, your screenshots show that the sites *are* Marked as Untrusted. If that wasn't done by you, this might be a different NoScript bug from what's already reported.

I'll check something and report back.

[barbaz]

Looks like this is the same long-standing bug with visiting Untrusted sites. But with Scripts Globally Allowed, it only takes one mis-click in the NoScript menu to trigger it.

anna, do you see the problem if you set about:config > noscript.docShellJSBlocking to 0? This is only a test, I'm not sure how safe it is.

[anna]

thanks barbaz, noscript.docShellJSBlocking=0 seems to have fixed it (e.g. context menu at serverfault now shows the correct list of currently disallowed domains instead of only showing "Allow [<http://serverfault.com>]")

[anna]

there are some strange things about this being a the same old bug though:

* I've only encountered the issue recently, and on two different machines (but with the same version of FF);
* one of the sites that had the issue today has never been visited before, so it seems unlikely it could have been marked as untrusted (unless marking a domain as untrusted also triggers a bug, there's higher chance of that, true);

[anna]

erm, strike the 'fixed it' part --- I've only checked it with with sites from the screenshots, and they do work now
however on some other sites JS is blocked and the menu shows the same "Allow [<full-address>]" that doesn't do anything

[myki]

It worked for me, I didn't test very far but it seems to work as before.

A last question, for me :
Do I have to set it back to 1, please ?

[barbaz]

Thanks all.

A last question, for me :
Do I have to set it back to 1, please ?

I would, at least until Giorgio responds to viewtopic.php?p=85615#p85615

erm, strike the 'fixed it' part --- I've only checked it with with sites from the screenshots, and they do work now
however on some other sites JS is blocked and the menu shows the same "Allow [<full-address>]" that doesn't do anything

That part might not be the same old bug. I'm not sure.

there are some strange things about this being a the same old bug though:

* I've only encountered the issue recently, and on two different machines (but with the same version of FF);

Recently something changed that this bug is now much easier to reproduce. Previously, it required A) clicking a link from a whitelisted site to an untrusted site, B) using the Back button.

It no longer matters how you visit the Untrusted site, nor how you then go to the next site.

* one of the sites that had the issue today has never been visited before,

The bug occurs when you visit a site you've Marked as Untrusted before visiting a site with scripts allowed. So that's not really surprising.

(unless marking a domain as untrusted also triggers a bug, there's higher chance of that, true);

It does for me when I set Scripts Globally Allowed.