"Allow scripts globally" shouldn't be sticky

[ChrisS]

Occasionally for a web site I know (e.g. my bank) I'll "Allow Scripts globally", rather than clicking "accept all temporarily" a bunch of times.

However - if I forget to turn it off, well, I'm getting no protection. Shouldn't a dangerous setting like this automatically reset to safe when the browser is restarted?

[therube]

Code: Select all

v 1.1.8.3
==========================================================================
+ The "noscript.tempGlobal" about:config preference causes the 
  "Globally Allow" status to be revoked at the end of each session

[Thrawn]

May I ask why you don't permanently whitelist your bank?

[therube]

If JavaScript is enabled ...

You are timed out after period of inactivity
You must agree to terms/conditions (that you can bypass otherwise)
More "stuff" goes on

...

[Thrawn]

In that case, as an alternative to globally allowing scripts, may I suggest the Tab Permissions addon?

[therube]

Why?
What is Tab Permissions & what is it going to do for me more then NoScript?

[Thrawn]

Tab Permissions allows you to enable/disable JavaScript (and images, plugins, frames, or redirects) on a per-tab basis. So, you could permanently whitelist your bank in NoScript, but then disable JavaScript in any tab that's annoying you.

I use it to set default-deny for images, in conjunction with Host Permissions (to permanently whitelist sites).

[therube]

This, https://addons.mozilla.org/en-us/firefox/addon/tab-permissions/?

[Thrawn]

Yes.

Best used in conjunction with Host Permissions.