Globally Allow Does Not Revoke

[GµårÐïåñ]

Shouldn't the globally allow be revoked when the browser is closed and restarted? I have noticed that if you do globally allow, the access remains active across sessions no matter how many times you close and restart unless you explicitly revoke it. When did this change to this behavior model?

[Alan Baxter]

If I recall correctly, the default has always been that way. Toggle noscript.tempGlobal to true.

[GµårÐïåñ]

I know but that toggle was supposed to make that not so. I have that toggle you mentioned as well set to true, so why is it still happening. This is why I brought it up, otherwise you are right, I know its normal behavior. I guess I should have been more clear, just figured it would be assumed.

[Alan Baxter]

I have that toggle you mentioned as well set to true, so why is it still happening.

I don't know. I just verified the toggle still works in a clean profile.

[GµårÐïåñ]

I actually switched to another profile for a client to test their site. When I came back a few hours later, I opened my own profile that I use and had noticed the problem and found it working again. SO not sure what the hell happened but its not doing it anymore. I will keep an eye on it but this allow globally is not something i do often enough and will be annoying to keep testing.

[Alan Baxter]

Glad to hear it's not doing it anymore, and I hope the issue doesn't come back for you. Stuff like that can be a pain.

[GµårÐïåñ]

Yeah because if its something that is wrong or broken, I can fix but when its a phantom glitch with no trace so we know how it happened, it leave me unfulfilled, uncertain and pissed that I don't know how it got fixed.