I like ths from Comodos Firewall and his "Installation Mode", which goes to the previous save setup after x minutes.
I whish, NoScript has this for the "Allow Javacript Globally", that NoScript returns after x min. to the save setup without Javascript and an additional choice, if the actual page loads again without Javascript or only for the following pages (my favour)
I use the "Allow Javacript Globally" from time to time and then, i forgett to switch back to often and with the x min. returning, it would be much safer for me .
Feature Request: "Allow Javascript Globally" only for x min.
Feature Request: "Allow Javascript Globally" only for x min.
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.13) Gecko/2009073022 Firefox/3.0.13 (.NET CLR 3.5.30729)
- Giorgio Maone
- Site Admin
- Posts: 9526
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Feature Request: "Allow Javascript Globally" only for x min.
Not sure if I want to add more clutter to options.
At this moment, though, the most similar thing you've got is noscript.tempGlobal about:config preference: if you toggle it to true, "Allow scripts globally" will last only until you restart your browser.
At this moment, though, the most similar thing you've got is noscript.tempGlobal about:config preference: if you toggle it to true, "Allow scripts globally" will last only until you restart your browser.
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
Re: Feature Request: "Allow Javascript Globally" only for x min.
OK, interesting tip, better than nothing 
But why not use the noscript.tempGlobal for this? FALSE, TRUE and x min.? Just an idea.

But why not use the noscript.tempGlobal for this? FALSE, TRUE and x min.? Just an idea.
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.13) Gecko/2009073022 Firefox/3.0.13 (.NET CLR 3.5.30729)
- GµårÐïåñ
- Lieutenant Colonel
- Posts: 3370
- Joined: Fri Mar 20, 2009 5:19 am
- Location: PST - USA
- Contact:
Re: Feature Request: "Allow Javascript Globally" only for x min.
With apologies to Giorgio for stepping in here and if he feels I am out of line please delete the post but as a developer myself I have to add a little something to give a bit of perspective if nothing else. For most people the addition of a feature seems to be a simple, put this in there like this or can't you make it do this or say this or like this or like that. I have heard things like, its only an extra checkbox, or its only an extra variable; but from the actual programming perspective of it, there is A LOT more to it.
Not always, granted, but most of the time it requires a rewrite or a serious modification of a code logic, regression and tie ins with other portions of the code to make a "simple" request work or function properly or efficiently and it is often not a reasonable risk for the developer to go tweaking the code which could lead to serious introduction of flaws in the core function just to add a feature that serves very little, or low priority benefit. Not to say that the developer won't consider it or do it but I think there needs to be a serious understanding of how much work actually goes into coding and "adding" features.
Personally, I would love to see a feature like this, although given how often I restart my browser, the current provided setting pretty much does the same thing for me but just wanted to add that its often more complicated to add a small tweak than it is to add a whole new feature. Perhaps not in this case, a pretty solid logic block should be able to take care of this but would require a timer hook and several other things that might even be a hindrance to the performance. Sorry to go on so long, just saying.
Not always, granted, but most of the time it requires a rewrite or a serious modification of a code logic, regression and tie ins with other portions of the code to make a "simple" request work or function properly or efficiently and it is often not a reasonable risk for the developer to go tweaking the code which could lead to serious introduction of flaws in the core function just to add a feature that serves very little, or low priority benefit. Not to say that the developer won't consider it or do it but I think there needs to be a serious understanding of how much work actually goes into coding and "adding" features.
Personally, I would love to see a feature like this, although given how often I restart my browser, the current provided setting pretty much does the same thing for me but just wanted to add that its often more complicated to add a small tweak than it is to add a whole new feature. Perhaps not in this case, a pretty solid logic block should be able to take care of this but would require a timer hook and several other things that might even be a hindrance to the performance. Sorry to go on so long, just saying.
~.:[ Lï£ê ï§ å Lêmðñ åñÐ Ì Wåñ† M¥ Mðñê¥ ßå¢k ]:.~
________________ .: [ Major Mike's ] :. ________________
________________ .: [ Major Mike's ] :. ________________
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2