InformAction Forums

I've noticed that (sometimes?) a single left click on the NS icon in the add-on bar in FF12 has the effect of allowing the current site (don't know if temporarily or permanently). It used to show a list of domains/subdomains and require a second click before allowing anything. Did the behavior of that icon change, or is something on my end messed up?

Unfortunately, I can't reproduce this effect reliably. It seems as if ~30% of the time the click on the icon automatically activates the bottom option of the popup menu. It's entirely possible that NS has nothing to do with this, because I've also noticed other weird effects when left clicking in FF since the last update (for example, new foreground tabs needing two clicks on a link, one to give the document focus, and one to activate the link).

It works fine for me, regardless of whether the icon is in the toolbar (top) or add-on bar (bottom).
You did check NoScript Options > General "Left clicking on NoScript toolbar button toggles permissions for current top-level site", correct?

Guestling wrote:I've noticed that (sometimes?) a single left click on the NS icon in the add-on bar in FF12 has the effect of allowing the current site (don't know if temporarily or permanently).

It's temporary, until you either click "Revoke Temporary Permissions", or close the browser.

Guestling wrote:Unfortunately, I can't reproduce this effect reliably. It seems as if ~30% of the time the click on the icon automatically activates the bottom option of the popup menu. It's entirely possible that NS has nothing to do with this, because I've also noticed other weird effects when left clicking in FF since the last update (for example, new foreground tabs needing two clicks on a link, one to give the document focus, and one to activate the link).

That definitely suggests that it's not NS. More likely is an extension conflict or a corrupt profile.

Please create a clean profile from scratch. Install only NoScript, leaving all the defaults.
Does the problem still exist? If not, NoScript is not the culprit.

Try adding back your extensions, one at a time, until you find the one that causes the issue.
Then remove all the others, pairing only the suspected one with NoScript, to confirm that the remaining one is the issue.
If the problem is solved even with all add-ons reinstalled, then the previous profile was probably corrupt. Problem solved.

Let us know, thanks.