REDUX: Why must I"Temporarilyallowallthis page"REPEATEDLY

[Jasong222]

Hey guys-

So I saw that thread and was going to post a 'me too', but in the comments it seemed that the thread got off track, or at least, maybe the subject was different than what I am thinking.

The situation:

Say I have a page open, and it's one of those with a long script list...
Say for whatever reason I'm tired of poking around the find the one line item script I need to allow, and say fuck it, and temp. allow them all.
Often, when the page reloads, MORE OTHER scripts appear and fail to load because they of course are blocked. But often, the feature I'm trying to get at STILL won't function.
So I temp. allow all again.

And the whole thing repeats: More scripts show up, I still can't get at the function I'm looking for.


Is it possible to have a "Temporary Allow All" Loop/reload/repeat function where NoScript will allow all the scripts, and then reallow all scripts over and over until all the scripts are allowed and no more new scripts show up on the list?

That way I only have to hit "temp allow all this page" once and then wait while NS goes through the over and over bit until all the scripts are allowed completely? (Actually, I'd probably use it two or three times, because I'd probably try allowing just one script once or twice and then only once I saw that there were many layers of scripts would I get fed up and then try to due the multiple/layered temp. allow all.

I'd call it- Universal Temp Allow All or Drilldown taa or Layered or Deep or something...

(I'm not suggesting that this replace the current behavior of the current TAA function... I'm suggesting an additional function.)


Any thoughts?


-J

[therube]

Why must I "Temporarily allow all this page" REPEATEDLY?

[Jasong222]

Hey-

Ok.. 'Guilty'-

I read the OP, saw that it was what I was talking about, and assumed that the OP was asking a question. Then, reading some of the replies, it seemed that the thread was hijacked and rest of the comments were about a totally different situation.

(Full disclosure- I only scanned the replies, but they all seemed to be about the 'new' topic.

I see that further on "allow scripts globally" (ASG) solves my problem. (I rarely use it, but recall that this is a 'temporary' solution, these permissions are not whitelisted, they are only allowed while ASG is turned on... Yes?)

BUT- just by way of saving a little face here- I'll add: With the whole "permissions for this site ONLY" controversy, and ABE and the functions coming in the new version- It would be nice, still, to only ASG for the site that I'm on ONLY, and not for all the scripts for all the open tabs/windows that I have.

BUT (but), I'll just say again, thanks for pointing that out, I missed it the first time. And it helps. Apologies for any inconvenience....


-Jason

[Thrawn]

Thanks for going and reading the original post when you were pointed to it .

The trouble with this kind of loop is that the site could import literally any script at all, and you've given pre-approval to it. So it is actually the same as allowing globally.

I'd suggest taking a few extra seconds to figure out what's needed. If you're going to come back regularly, then it's worth taking the time to set permanent permissions for the sites you actually need. And if not, then you probably don't know enough about this site to trust it so implicitly...