Revoke Temp Permission question

[bjm_]

Hello
I have read and re-read FAQ's especially 5.2
I have set all 5.2 to false and still when I Revoke Temporary Permission on current tab.
All open tabs Revoke Temporary Permission.
Isn't there a way to set Revoke Temporary Permission to just act on the current tab
and leave all other open tabs with Temporary allow setting.
When I prompt Revoke on one tab. All open tabs Revoke wo reload.
I want to be able to Revoke on current tab only and not affect other tabs.
I browse in a sandbox. So, it's not practical for me to whitelist.
And I prefer to work with NoScript defaults.
I just want to Revoke on current tab, move to another tab and not have Temporary allow setting for that tab changed back to default.
What am I doing wrong?

Thanking you in advance

[therube]

"Permissions" are revoked for all affected tabs.
"Refresh" can be confined to only the current tab (or none, or all).

> leave all other open tabs with Temporary allow setting

Not an option.

[bjm_]

"Permissions" are revoked for all affected tabs.
"Refresh" can be confined to only the current tab (or none, or all).

> leave all other open tabs with Temporary allow setting

Not an option.

Guess, that's why I couldn't get what I wanted.

Not an option

So, what is the intended purpose of Disable Auto Reload
I thought I found my solution when I read

Q: When I change permissions, all the affected tabs/windows are reloaded, and sometimes this is annoying. I know I could turn off automatic reloading from NoScript Options|General, but can I disable it for background tabs/windows but keep it for the current tab only? A: Yes, you can: just toggle the noscript.autoreload.allTabs about:config preference to false.

When I Revoke Temp Permission. I am changing permissions. The answer

Yes, you can: just toggle the noscript.autoreload.allTabs about:config preference to false

suggested to me I could act on the current tab and disable the action on the background tabs.
Clearly after using NoScript for years. I still don't understand the purpose of auto reload true or false.
I'm running with 10 tabs open with all Auto Reload options false. Each has it's own set of Temp allow. For security I wanted to Revoke on the 8 tabs I wasn't using at the time...but, planned to come back to. If I Revoke on any tab. Revoke is invoked for all tabs.
Why run with Auto Reload true or false. &
Is there a suggestion box.
Thank you for your quick and concise reply

[barbaz]

Please don't cross-post / post multiple topics on the same issue as it makes it hard for people to properly follow up your posts.
Anyway, what you want is basically the same idea as viewtopic.php?f=10&t=17144

And yeah, about:config -> noscript.autoReload.allTabs* prefs aren't going to have quite the same effect as per-tab permissions because revoke temporary permissions stops JS execution on Temp-Allowed sites even if it doesn't reload them.

Is there a suggestion box.

Post your idea somewhere on these forums and Giorgio will see it. This topic will do.

[bjm_]

Please don't cross-post / post multiple topics on the same issue as it makes it hard for people to properly follow up your posts.
Anyway, what you want is basically the same idea as viewtopic.php?f=10&t=17144

And yeah, about:config -> noscript.autoReload.allTabs* prefs aren't going to have quite the same effect as per-tab permissions because revoke temporary permissions stops JS execution on Temp-Allowed sites even if it doesn't reload them.

Is there a suggestion box.

Post your idea somewhere on these forums and Giorgio will see it. This topic will do.

posting.php?mode=quote&f=10&t=20059&p=71697#preview
Why not Development and enhancement
My apologies to the cross posting monitor. I was not aware I was cross posting my support request by requesting an enhancement to NoScript.

Anyway, what you want is basically the same idea as viewtopic.php?f=10&t=17144

Respectfully, I do not run Private Browsing.

And yeah, about:config -> noscript.autoReload.allTabs* prefs aren't going to have quite the same effect as per-tab permissions because revoke temporary permissions stops JS execution on Temp-Allowed sites even if it doesn't reload them.

I found that out by trial and error. But, presumed my testing was flawed. So I posted to Support for help.
Since, this Topic will do.
Please consider my request for a per tab Revoke Temp Permissions option. Revoke Temporary Permission to act on the current tab
and leave all other open tabs with Temporary allow setting.
Respectfully submitted

[barbaz]

Please consider my request for a per tab Revoke Temp Permissions option. Revoke Temporary Permission to act on the current tab
and leave all other open tabs with Temporary allow setting.

Just had an idea: You're using Firefox 32 so it is possible for NS to do what you want. In fact, it behaved exactly that way in NoScript 2.6.8.20rc1 when auto reloading was disabled...

I think an about:config-only pref to toggle realtime permission changes could potentially be useful for developer testing also, e.g. to monitor a long running script on one site while doing normal browsing in the same browser session.

[bjm_]

Please consider my request for a per tab Revoke Temp Permissions option. Revoke Temporary Permission to act on the current tab
and leave all other open tabs with Temporary allow setting.

Just had an idea: You're using Firefox 32 so it is possible for NS to do what you want. In fact, it behaved exactly that way in NoScript 2.6.8.20rc1 when auto reloading was disabled...

I think an about:config-only pref to toggle realtime permission changes could potentially be useful for developer testing also, e.g. to monitor a long running script on one site while doing normal browsing in the same browser session.

So, my solution is to go back a version or so. What does the rc1 stand for? Release candidate 1
So, I have to go back to a beta to get the behavior I want....interesting
For now I think I'll run with all autoReload = false and toggle one at a time and see how it goes.
I don't need 10 - 15 pages reloading at the same time. When all I want is one page to reload.
Thanks
Respectfully

[barbaz]

So, I have to go back to a beta to get the behavior I want....

You don't have to use a beta if you don't want to. NoScript 2.6.8.19 would work for you also.
I just linked the latest version of NoScript which didn't have realtime permissions in Gecko >= 28, for reference.

But in my experience, generally (but not always) the beta versions aren't any less usable than the release versions, and I don't recall any showstopper issues with 2.6.8.20rc1.

[therube]

URL: http://www.w3schools.com/js/tryit.asp?f ... ming_clock

Revoke Temporary Permission to act on the current tab
and leave all other open tabs with Temporary allow setting.

it is possible for NS to do what you want. it behaved exactly that way in NoScript 2.6.8.20rc1 when auto reloading was disabled...

I think an about:config-only pref to toggle realtime permission changes

Now how did you know that?
And it was what that allows this?

(And I suppose it was not this:
> Implemented early permission changes enforcement on not yet reloaded
> pages, to better match the old CAPS-based behavior
Or did it have to do with 1005552?)

And what was the change in later versions that this behavior changed?


In any case, using this "feature", I'd think you'd really need to be aware of where you are & what you have done on a particular page, otherwise you'd just end up, confused.


(So it was "this".)

[bjm_]

@ Topic
Thanks to therube & barbaz & Giorgio

Respectfully
bjm_

[barbaz]

Revoke Temporary Permission to act on the current tab
and leave all other open tabs with Temporary allow setting.

it is possible for NS to do what you want. it behaved exactly that way in NoScript 2.6.8.20rc1 when auto reloading was disabled...

I think an about:config-only pref to toggle realtime permission changes

Now how did you know that?

viewtopic.php?f=7&t=19474&start=15#p69018

In any case, using this "feature", I'd think you'd really need to be aware of where you are & what you have done on a particular page, otherwise you'd just end up, confused.

Which is why, if an option for that does get introduced in NoScript, IMO it should not have a GUI, but rather stay in about:config.