Feature Request:Allow all this page should work after reload

Bug reports and enhancement requests
Post Reply
gmoises
Posts: 1
Joined: Sun Oct 18, 2009 7:07 pm

Feature Request:Allow all this page should work after reload

Post by gmoises »

Feature Request: The "Allow all this page" option should really do that.

Too many times,I select this option, then after the page reloads, there are more sites blocked, again and again.

The user should be able to select this option only once per page.

Thank you for this great extension.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Tom T.
Field Marshal
Posts: 3620
Joined: Fri Mar 20, 2009 6:58 am

Re: Feature Request:Allow all this page should work after reload

Post by Tom T. »

It always works for me. BUT....

Unfortunately, a growing trend seems to be that when you allow Scripts A, B, and C, and the page reloads, those scripts, or the reloaded page, will try to load *new" Script D, Objects E and F, etc.

Sometimes this happens for several generations, i. e., I've allowed the scripts, seen new ones try to load, allowed, then even more new ones try to load ... etc.

Please review the times that it doesn't work. If the scripts or objects that are *not* being allowed by your "allow all this page" are different from those requesting permission the first time, then it seems there is not a good solution. NoScript can't predict which scripts a newly-refreshed page will try to load.

One poster suggested that "allow all this page" should allow *all future* scripts on that page. This is dangerous. Suppose Bad Guy has arranged that when Good Script A is loaded, it then attempts to load evilsite.cn (China, not to pick on them or anything). It is for your protection that each script or object attempting to load must be viewable by you first, so that you can make this decision.

If the scripts and objects that are not being permitted after the reload are *identical* to those in the list when you clicked "allow all this page", then that is a different issue. Please test this out and let us know which is the case. Thanks, and thanks for the kind words on NoScript. They're appreciated.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20
Post Reply