"temporary allow all this page" does not allow all

[al_9x]

It only allows scripts it knows about at the time of invocation. Any new ones, dynamically added by previously blocked scripts, are not allowed. I think the typical usage for temp allow all is to see if the page works with no script blocking, so it would be better if it actually did allow everything.

[Alan Baxter]

I prefer the current implementation. I want to know which sites will be allowed before I make that selection. On the rare occasion that I want to allow scripts from all sites, sight unseen, I select Allow scripts globally, which seems to be what you are effectively asking for anyhow.

[al_9x]

I want to know which sites will be allowed before I make that selection

I can see the logic in cautiously allowing only the currently shown blocked, but then it should be called "temp allow currently blocked," and there should be a separate temp allow all this page, where all actually means all, and which does not necessitate allowing globally.

A true "temp allow all" would be very useful for trouble-shooting, when you need to quickly see what an unblocked page looks like and also for inexperienced users that get exasperated trying to make a page work. It would be better to give them something that works in one click, rather than them disabling blocking globally or uninstalling in frustration. For this purpose, temp allow all this site, would be also helpful.

[Alan Baxter]

I want to know which sites will be allowed before I make that selection

I can see the logic in cautiously allowing only the currently shown blocked,

Giorgio has repeatedly said he thinks it's dangerous to allow sites that are called by scripts that haven't been allowed yet, i.e. allowing sites that aren't listed in the NoScript menu. You wouldn't want to allow pwnme.cc by accident, would you? That said, I also agree with you somewhat. (See below)

but then it should be called "temp allow currently blocked,"

That name is misleading too, since everything not explicitly whitelisted is blocked: both the sites that are listed in the NoScript menu and the ones that aren't. But the current "Temporarily allow all this page" is misleading. It implies it will allow every script the page wants, not just the ones that NoScript happens to know about already.

and there should be a separate temp allow all this page, where all actually means all, and which does not necessitate allowing globally.

A true "temp allow all" would be very useful for trouble-shooting, when you need to quickly see what an unblocked page looks like and also for inexperienced users that get exasperated trying to make a page work. It would be better to give them something that works in one click, rather than them disabling blocking globally or uninstalling in frustration. For this purpose, temp allow all this site, would be also helpful.

I agree this feature would be useful, albeit dangerous. Personally, I have dedicated, sandboxed, Firefox profiles that I run with the -no-remote option for this purpose: one profile with NoScript and one without. Much safer, but not something I would expect NoScript users to do.