Menu suggestion, Rules specific to page URL/domain, More

Bug reports and enhancement requests
Post Reply
Scripty
Posts: 7
Joined: Thu Nov 03, 2011 4:19 pm

Menu suggestion, Rules specific to page URL/domain, More

Post by Scripty »

Something I run into alot using NoScript, is wanting/requiring scripts from a source to work on example1.com but never on exmple2.com. Could we have an option to always allow scripts from a source on only certain site(s)/domain(s). I can't remember the specific sites right now but I've run into this often over the years, browsing multiple sites in tabs and allowing certain scripts on one site because you want or require them, but then another site where you don't want it will suddenly also have them allowed.

While NoScript can sometimes be a godsend on some sites, it's menu and rules options could be better, personally.

As a thought or example for the menu...
Image
(By "locally" I mean in regards to the currently browsed site/domain)
(used "Toggle" as in (de)selecting an already chosen option will return it to the default state when first encountered)

Now I could see some might not like the menu done like that because it would add a "step" to doing a temporary allow to a main "top level" site which is probably the most common action, but that could be alleviated. With a menu as in the picture each click on informaction.com itself could cycle through the options in the submenu without having to use the submenu (the first click could be the most commonly used temporary allow).

Also if the informaction.com icon would change in colour to represent it's current rule state it would make it easy to look through the list and see the state for scripts from each location on a page, it would also make the reverse easy, ie finding a script by it's state simply by looking for the colour associated to the state your looking for. eg: there may be a script that's running that you don't want on that site, looking for green? icons would be an easy way to spot any running scripts one might want to deny, or looking for red? when trying to find something that's blocked. People are very good at trying to find something by looking for it's colour first.

Also this would make the main menu almost half as long since each site will only be listed once on it.

This would also remove the need for an "Untrusted" option, from my understanding all sites seem to be "Untrusted" by default with the only result of marking them "Untrusted" hiding it in the "Untrusted" submenu, perhaps in an attempt to keep the length of the menu down, as mentioned a menu as in the picture would be much shorter. Though perhaps I'm missing something about marking something as "Untrusted"

There was something else but it's slipped my mind while typing this.

Anyway just my two cents.

Oh one more thing, an option to allow all on current page would be appreciated. I was browsing a few threads and read something about an explanation why it works the way it does but lets face it, NoScript users are not your average web browsers, installing something like NoScript already shows they're security conscious and know what allow all means and it's risks. Instead of trying to protect them from themselves (ie treating them like children) options to "Allow all current" and "Allow all" would be appreciated.

Thanks.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
dhouwn
Bug Buster
Posts: 968
Joined: Thu Mar 19, 2009 12:51 pm

Re: Menu suggestion, Rules specific to page URL/domain, More

Post by dhouwn »

Scripty wrote:Also this would make the main menu almost half as long since each site will only be listed once on it.
Similar to the ideas discussed at http://forums.informaction.com/viewtopi ... =10&t=9250 and probably before in NoScript's lifetime.
Would love to see something saving vertical space being implemented.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0
User avatar
therube
Ambassador
Posts: 7969
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: Menu suggestion, Rules specific to page URL/domain, More

Post by therube »

> allow scripts from a source on only certain site(s)/domain(s)

ABE - Application Boundaries Enforcer
What is ABE?
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20120812 Firefox/16.0 SeaMonkey/2.13a2
User avatar
GµårÐïåñ
Lieutenant Colonel
Posts: 3369
Joined: Fri Mar 20, 2009 5:19 am
Location: PST - USA
Contact:

Re: Menu suggestion, Rules specific to page URL/domain, More

Post by GµårÐïåñ »

dhouwn wrote:
Scripty wrote:Also this would make the main menu almost half as long since each site will only be listed once on it.
Similar to the ideas discussed at http://forums.informaction.com/viewtopi ... =10&t=9250 and probably before in NoScript's lifetime.
Would love to see something saving vertical space being implemented.
Why would you link the same topic we are in as a reference for something being discussed? 9250 is this topic, so why would you link to it again as if it was something different?
~.:[ Lï£ê ï§ å Lêmðñ åñÐ Ì Wåñ† M¥ Mðñê¥ ßå¢k ]:.~
________________ .: [ Major Mike's ] :. ________________
Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
dhouwn
Bug Buster
Posts: 968
Joined: Thu Mar 19, 2009 12:51 pm

Re: Menu suggestion, Rules specific to page URL/domain, More

Post by dhouwn »

Oops, mean to link to http://forums.informaction.com/viewtopi ... =10&t=9226. Seems like I was on the wrong tab when copying the URL bar.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20120812 Firefox/16.0
User avatar
GµårÐïåñ
Lieutenant Colonel
Posts: 3369
Joined: Fri Mar 20, 2009 5:19 am
Location: PST - USA
Contact:

Re: Menu suggestion, Rules specific to page URL/domain, More

Post by GµårÐïåñ »

That's fine, thank you. I just wanted to make sure we had the right resource in the discussion, specially if its useful.
~.:[ Lï£ê ï§ å Lêmðñ åñÐ Ì Wåñ† M¥ Mðñê¥ ßå¢k ]:.~
________________ .: [ Major Mike's ] :. ________________
Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Post Reply