InformAction Forums

"Temporarily Allowing All Permissions This Page"...
Should Mean ALL PERMISSIONS, one click, done deal.
I feel that it should not be necessary to re-select that option repeatedly,
before the basic features of a webpage finally begin to work properly.
Please enhance the program so that users only have to click this one time,
and the page will come back all clear, and stay that way.
For example, in order to use the picture ZOOM feature on the following webpage,
requires Temporarily Allowing ALL the Permissions for this page... 14 or 15 times over!
http://www.rgj.com/article/20120128/NEW ... on-fit-fat
I realize the page must be adding more as I go,
but I'm hoping your program can be enhanced or improved to adapt to that occurrence.
Sorry if this has been addressed previously, but I could not find it listed here.
& btw, I'm always using the current version of NoScript, as it updates automatically: 2.2.9rc1
Thanks.

About the only way around something like that, would be to Allow Globally, dangerous in itself, then refresh the page. (Settings could be set such that an Allow Globally would only refresh the current page on its initialization.) Then you would want to be sure to disable Allow Globally after you have finished with the page.

WOW, you weren't kidding about the 14 or 15, that's awful! (And I also had to disable Adblock Plus.)

Tom (I think it is) has some good explanations why a TAA cannot allow "everything" (at once), & why it is dangerous to do so.


Now, just what was that last item I allowed?
If that can be found, & if that alone is sufficient to allow, then you could use ABE to have that particular domain restricted to running only on the rgj.com domain.


It was legolas-media.com, though that & rgj.com alone are not sufficient.
Perhaps you could come up with some combination that worked, but that looks to be a true PITA.

I too wondered why "temporarily allow all" isn't recursive, but has to be executed repeatedly (sometimes very repeatedly!) for some pages.

I do understand the point about a "one-click" function being potentially unsafe. But many of the pages I visit generate very long lists of allow/disallow entries and the "temporarily allow all" function is all the way down near the bottom. It is cumbersome and sometimes a little annoying to have to scroll down through these lists repeatedly just to reach the "temporarily allow all" function every time.

In lieu of a "one-click" solution, could the "temporarily allow all" function be moved to the top of the scrolling list? Or could we have a toolbar button that, when clicked, issues the "temporarily allow all" function? (When there are no more to allow the button can grey-out.)

I'd happily live with repeated button clicks and/or being able to select the function quickly from the top of the scrolling list, as a reasonable compromise to the "one-click" solution.

Thoughts?

Kind regards,
--appyface

appyface wrote:Or could we have a toolbar button that, when clicked, issues the "temporarily allow all" function?

There already is one. Look in the Customize dialog for it. Right-click any toolbar, then select Customize.

I've looked in the customize toolbar dialog in the past, and never saw the buttons... but I do see them today! Thank you very much, works for me.

appyface wrote:I too wondered why "temporarily allow all" isn't recursive, but has to be executed repeatedly (sometimes very repeatedly!) for some pages.

I do understand the point about a "one-click" function being potentially unsafe. But many of the pages I visit generate very long lists of allow/disallow entries and the "temporarily allow all" function is all the way down near the bottom. It is cumbersome and sometimes a little annoying to have to scroll down through these lists repeatedly just to reach the "temporarily allow all" function every time.

In lieu of a "one-click" solution, could the "temporarily allow all" function be moved to the top of the scrolling list? Or could we have a toolbar button that, when clicked, issues the "temporarily allow all" function? (When there are no more to allow the button can grey-out.)

I'd happily live with repeated button clicks and/or being able to select the function quickly from the top of the scrolling list, as a reasonable compromise to the "one-click" solution.

Thoughts?

Kind regards,
--appyface

There is extensive discussion all over this forum on why this is the way it is and will always be this way and nothing will change on this for the time being. Search for it and read up.

therube wrote:Tom (I think it is) has some good explanations why a TAA cannot allow "everything" (at once), & why it is dangerous to do so.

This is probably the best one, and reasonably concise.

I'm going to bookmark it for the many times it will come up in the future.
(And maybe ask to add it as a sticky in the forthcoming separate sub-forum of guides, docs, hints, etc.)

Maybe it should be also added to the FAQ.

dhouwn wrote:Maybe it should be also added to the FAQ.

Actually, it's already in the NoScript "Features" Page:

Allow all this page and Temporarily allow all this page enable every site shown as allowable by NoScript's menu on the current page, unless already marked as untrusted.

which apparently isn't read any more commonly than the FAQ.

But it does require a bit of inference or understanding to realize that the above does not allow succeeding generations of scripts called by previously-allowed ones after the page reload, and no, it doesn't explain why it would be unsafe to change it.

I'll ask Giorgio to take a look at the idea. He's already approved the sticky post; just awaiting his reply on where.

dhouwn wrote:Maybe it should be also added to the FAQ.

For the love of all that is holy, its common sense. I just think people refuse to THINK for a sec before throwing a tantrum. That being said, I am not at all opposed to the suggestion of adding it to the FAQ, if people actually freakin read the darn thing.

GµårÐïåñ wrote:For the love of all that is holy, its common sense. I just think people refuse to THINK for a sec before throwing a tantrum. That being said, I am not at all opposed to the suggestion of adding it to the FAQ, if people actually freakin read the darn thing.

It has indeed been made a sticky, near the top of NoScript > Support.