why doesn't "temporarily allow" do that?

[soi]

I have a minimal whitelist, so when I go to a new site I rarely visit, and it contains lots of "rich content," noscript will block it (as I would like it to)

on the occasions I decide to "temporarily allow all this page" so I can view this content, nothing changes, I can't see the content. but when I view the URL in Chrome or IE, all the content is available

even to post on this forum, I could not see the CAPTCHA after I "temporarily allow all this page," so I had to use Chrome to see it and post here

this is the norm, not the exception. why doesn't "temporarily allow all this page" release everything (that is, "turn noscript off temporarily") as one might expect?

or am I missing something here?

thanks!

[therube]

Temporarily Allow All will allow all the domains at the time that you invoked TAA.

Once invoked, other domains may load, become visible, which were not there before. So you may need to TAA again. (And possible the same could happen yet again...)

[Guest]

[quote="therube"]Temporarily Allow All will allow all the domains at the time that you invoked TAA.
quote]

Thanks for your reply, but I don't think I follow.

My understanding is that selecting "temporarily allow all this page" effectively turns Noscript off for that page, effective the next reload, such that the page should now appear as though Noscript isn't even installed.

Yet it rarely works that way, while the page renders fine in Chrome and IE.

[lewisje]

If a request from a certain domain is only ever made from a particular script that happens to be blocked, NoScript will not know that that domain had a script on the page; then when you "temporarily allow" that first script, NoScript will see that a request from that domain was made, and instead of potentially introducing a security problem by auto-allowing that script too even though you may never have heard of the domain before, it will ask you whether you trust that domain too.

[therube]

> "temporarily allow all this page" effectively turns Noscript off for that page

No, it only (temporarily) allows those domains seen at the time you invoke TAA.
In the same way, domains introduced after the TAA are still not allowed, until you invoke TAA again (& possibly again & again ...).

There is no way of knowing ahead of time "what's coming next" to allow them "all" by using TAA.

There is no "Allow Scripts Globally - on this page only".


The closest you can get is to "Allow Scripts Globally (dangerous)", reload the page in question, do what you have to do, then disable "Allow Scripts Globally" so that other pages are likewise not affected.

[soi]

There is no way of knowing ahead of time "what's coming next" to allow them "all" by using TAA.

OK, I'm a little confused here. Are you saying that between the time that I initially load a page, and the time that I TAA for that page, that when the page then reloads "new" scripts will be loaded that will still be blocked because they were not seen 5 seconds ago, causing the page to not render properly? I find the likelihood of that to be small, at least on a regular, consistent basis. Not impossible, just very unlikely.

The closest you can get is to "Allow Scripts Globally (dangerous)", reload the page in question, do what you have to do, then disable "Allow Scripts Globally" so that other pages are likewise not affected.

Yeah, I guess so, thanks.

[therube]

> "new" scripts will be loaded that will still be blocked because they were not seen 5 seconds ago

The possibility exists.

> causing the page to not render properly?

The possibility exists.


Using a default whitelist...

Goto http://www.msn.com/
msn.com is allowed (by default)
s-msn.com (at the least) is not allowed
TAA
msn.com & s-msn.com are now both allowed
bing.com, which did not exist (5 seconds ago), is now visible, but not allowed
TAA
at that point, all domains seen; msn.com & s-msn.com & bing.com are all allowed

(I happen to have Adblock Plus too, which filters out some "ad" sites, so I don't see them - like say, questionmarket.com & likely others.)

Now are s-msn.com or bing.com necessarily needed? Perhaps, perhaps not. Would I necessarily allow them - no. If I noticed something not working, I would explore why & if I found it was one of those two domains, then I may temporarily allow to get whatever feature it was to work.

[soi]

Here is a sample page:

http://www.bloomberg.com/news/2011-10-0 ... sales.html

I have Allowed Scripts Globally, disabled Adblock Plus, whitelisted Bloomberg.com in Ghostery and enabled persistent cookies, and yet the content of this article is pushed way down the page, so that I have to scroll way down to read it.

By contrast, it renders fine in Chrome and IE.

I'm baffled.

[Alan Baxter]

http://www.bloomberg.com/news/2011-10-0 ... sales.html

Your problem may be caused by one of the sites you have marked as Untrusted. Those are not enabled even when scripts are globally allowed. That page renders fine for me with NoScript's default settings if I Allow Scripts Globally. That's with no other extensions installed.
NoScript 2.1.4rc2

[Guest]

>Your problem may be caused by one of the sites you have marked as Untrusted.

Thanks, but Bloomberg.com is not marked as untrusted.

BTW, in addition to the steps I took in my previous post, I also reset NS to its defaults.

I'm figuring it's gotta be some other extension causing this, and ABP is the most likely culprit, but I disabled it and the problem still persists. Ghostery maybe, but I whitelisted Bloomberg.com there.