Browser Restart Does Not Auto-Revoke Temp Permissions
-
El Cid
Browser Restart Does Not Auto-Revoke Temp Permissions
I have NoScript 2.5.9 + Firefox 16.0.2 and I've just noticed that if I quit all FF browser instances the old behavior was to cancel all temporarily set permissions. I am now finding that they 'persist' and have to always be revoked manually. How do I reinstate the older behavior?
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
Re: Browser Restart Does Not Auto-Revoke Temp Permissions
There shouldn't be any need to revert anything; temporary permissions ought to be cleared when all browser instances are closed.
Either there's something wrong with your system (you could try creating a second profile containing only NoScript, and seeing if it has the same problem), or Fx 16.0.2 has changed something.
Either there's something wrong with your system (you could try creating a second profile containing only NoScript, and seeing if it has the same problem), or Fx 16.0.2 has changed something.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0
Re: Browser Restart Does Not Auto-Revoke Temp Permissions
I just ran a test on Fx 16.0.2, temp-allowing a site, closed, restart, and the temp permission was properly revoked.
You could double-check in Windows Task Manager (Ctrl+Alt+Del) > Processes that all instances of firefox.exe have been terminated.
Mozilla has recommended closing Firefox by using File > Exit in this situation rather than the X box in the upper right, though I've never found it to be necessary.
If none of these help, then yes, an extension conflict is quite possible, so please follow Thrawn's advice about a clean profile with NoScript only.
If that solves the problem, you can narrow down the problem extension with Standard Diagnostic, or just pair each of your other add-ons, one at a time, with NS, until the culprit is found. Let us know, thanks.
You could double-check in Windows Task Manager (Ctrl+Alt+Del) > Processes that all instances of firefox.exe have been terminated.
Mozilla has recommended closing Firefox by using File > Exit in this situation rather than the X box in the upper right, though I've never found it to be necessary.
If none of these help, then yes, an extension conflict is quite possible, so please follow Thrawn's advice about a clean profile with NoScript only.
If that solves the problem, you can narrow down the problem extension with Standard Diagnostic, or just pair each of your other add-ons, one at a time, with NS, until the culprit is found. Let us know, thanks.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:16.0.2) Gecko/20100101 Firefox/16.0.2