At first, thanks for an extremally useful plugin. The only disappointment is the option "Update related pages automatically" because it almost always update ALL the pages opened in FireFox which take some time (from several seconds up to tens of seconds) which I definitely did not want to waste.
So I beg you: please, please add the new option "Update CURRENT page automatically" so that just current page to be updated when I change NoScript's permissions for this page.
"Update CURRENT page automatically" option, I beg you
"Update CURRENT page automatically" option, I beg you
Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9 (.NET CLR 3.5.30729)
Re: "Update CURRENT page automatically" option, I beg you
The internal option 'noscript.autoreload.allTabs' in about:config can help with it, but it looks like some kind of hacking. As an average user, I could not even imagine something like this exists. Of course, a native checkbox in NoScript's Settings would be much better.
Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9 (.NET CLR 3.5.30729)
-
- Ambassador
- Posts: 1586
- Joined: Fri Mar 20, 2009 4:47 am
- Location: Colorado, USA
Re: "Update CURRENT page automatically" option, I beg you
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10
Re: "Update CURRENT page automatically" option, I beg you
Unlike the other main browsers, Firefox/Seamonkey has developed in a community of users who wanted and got access to configuration tools extra to the GUI. Hence the use of about:config, while not for the complete novice IE refugee, is something most assuredly *not* anywhere like "hacking" - - it's just another kind of UI and all of us plain Mozilla users are familiar with it. You will also be, nowVitaliy wrote:The internal option 'noscript.autoreload.allTabs' in about:config can help with it, but it looks like some kind of hacking.

All Mozilla users are encouraged to become familiar with the wealth of flexibility that can be accessed via about:config and, indeed, it's to Giorgio's great credit that his FAQs have to the most part very clearly explained every pertinent NS preference that isn't - because the GUI would be simply overcrowded and confusing - in the preferences menu.As an average user, I could not even imagine something like this exists.
As pointed out above, Giorgio's decided that this particular preference is better not in the main menu. Maybe because not enough users have yet asked for the lazy man's option?Of course, a native checkbox in NoScript's Settings would be much better.

end of hijack.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10
Re: "Update CURRENT page automatically" option, I beg you
OK, I understand such point of view when thinking as a developer.
But, please, just try to think as an ordinary user.
When you select "Temporarily allow all this page", do you except this page to be reloaded or all the pages to be reloaded?
Please think about this question: do you know many people who expect all the pages to be reloaded when they select "Temporarily allow all this page"?
So, why 'noscript.autoReload.allTabs' is 'true' by default and there is no clear user-friendly way to turn it off in NoScript's options?
Let's imagine a situation. You wake up in the middle of the night. In the dark, you go to the bathroom and turn on the light there. But, when you turn the light in the bathroom on, the light is turned on everywhere in your house! This wakes up everyone in your house and they ask you: What's going on? And all you can say is: Oops, all I did was just turning the light in the bathroom on...
This is how the default behaviour of NoScript would look in the real life's situation.
Please don't think I'm cavilling at NoScript or something. No, I appreciate NoScript very much and I think it is very useful. But I just want to show you that user-friendly usability is important to an ordinary user in the same way as the highest-level technical implementation to a developer.
And my point of view is the following: 'noscript.autoReload.allTabs' is not a kind of additional or advanced option which just might be changed by someone. No! This is a core option of NoScript which is necessary in the Options window.
But, please, just try to think as an ordinary user.
When you select "Temporarily allow all this page", do you except this page to be reloaded or all the pages to be reloaded?
Please think about this question: do you know many people who expect all the pages to be reloaded when they select "Temporarily allow all this page"?
So, why 'noscript.autoReload.allTabs' is 'true' by default and there is no clear user-friendly way to turn it off in NoScript's options?
Let's imagine a situation. You wake up in the middle of the night. In the dark, you go to the bathroom and turn on the light there. But, when you turn the light in the bathroom on, the light is turned on everywhere in your house! This wakes up everyone in your house and they ask you: What's going on? And all you can say is: Oops, all I did was just turning the light in the bathroom on...
This is how the default behaviour of NoScript would look in the real life's situation.
Please don't think I'm cavilling at NoScript or something. No, I appreciate NoScript very much and I think it is very useful. But I just want to show you that user-friendly usability is important to an ordinary user in the same way as the highest-level technical implementation to a developer.
And my point of view is the following: 'noscript.autoReload.allTabs' is not a kind of additional or advanced option which just might be changed by someone. No! This is a core option of NoScript which is necessary in the Options window.
Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 (.NET CLR 3.5.30729)