Feature request: allow scripts globally for a time

[suggestion12]

Hi, I've got a feature request.

I would like to be able to allow scripts globally, as is possible now, but NoScript should disable scripts globally again after a time, e.g. 30 minutes or two hours.

Motivation: I often find myself allowing scripts globally when doing e.g. banking or e-commerce when I don't expect to be attacked, and when I don't want the site to break because of some disabled javascript dependency. However after banking/shopping/etc I forget to disable scripts globally. Having a timer would be very useful to decrease the possibility for user error.

Thanks for creating NoScript!

[barbaz]

How about allow scripts globally for a browser session? So you close the browser and scripts not globally allowed. I would think that's more usable for your use case anyway.
There's a pref for that which I've set, but I can't remember which it is... let me get back to you on that.

[therube]

(Not in a browser with NoScript ATM, but) *temp*Global kind of rings a bell.

In any case +1 for some sort of something or the other.
Even if it be an (optional) nag.
If Global, if Nag Option True, present Nag, Time > x:minutes.

Too often, when testing something, I'll Globally Allow, only to some time later come back & say, "oh damn, I left it on!".

The existing reset of Global Allow on browser restart is fine.

A strictly timed reset... eh, in general that's OK, but what if you actually didn't want it to reset, you actually wanted to remain in Globally Allowed.

So to me, a Nag would be better.
A beep, every so often, a "slide out" from the NoScript icon, every so often (hey! dumy! you're running Globally Allowed!) would be better IMO.


And I still think that a more discoverable Cascade would be a better option in most cases, to Allow Globally, potentially "safer" too.
viewtopic.php?p=74344#p74344

[barbaz]

Yes, thanks, that's it:

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
(thanks chconnor and Alan Baxter for suggestion)

@suggestion12: try going to about:config and setting noscript.tempGlobal to true - then all you have to remember is to close the browser when done with sensitive/financial sites.

[Thrawn]

Perhaps an even better option would be to create a separate Firefox profile for your banking?

You could use ABE to forbid all banking on your regular profile, and maybe forbid everything *except* banking on the second one. Then allow scripts globally on the dedicated banking profile.

[barbaz]

If they can't remember to Forbid Scripts Globally, are they going to remember to switch profiles?

[Thrawn]

and maybe forbid everything *except* banking on the second one.

[suggestion12]

@suggestion12: try going to about:config and setting noscript.tempGlobal to true - then all you have to remember is to close the browser when done with sensitive/financial sites.

Thanks, that's definitely better than relying fully on remembering. I still think my feature request has relevance, though.

Perhaps an even better option would be to create a separate Firefox profile for your banking?

You could use ABE to forbid all banking on your regular profile, and maybe forbid everything *except* banking on the second one. Then allow scripts globally on the dedicated banking profile.

That's a good suggestion for banking. But for e.g. e-commerce I won't know all the domains ahead of time.

[therube]

are they going to remember to switch profiles?

In my case, sure.
I have specific Profiles for specific reasons.
One Profile, the one I'm in now, is exclusively for informaction.