I've been a happy NS user for some time now, and have joined the forums to make a couple of feature requests. In this thread, I found a better suggestion which (when implemented) will give a better answer to the need that prompted my ideas. I still wanted to bring them up, because I think they may be easier to implement and/or someone else will see other uses for them.
1) When I temporarily allow, say googleapis.com, I usually do it for use in one site; I don't really want to allow it for other sites in the same session (not to mention, already open in other tabs).
2) Recently, such APIs have started to spread across domains; e.g. to really allow Google APIs, you sometime need to also allow google.com and gstatic.com etc.
My ideas were to solve these problems separately:
1) Make tab-specific permissions, and make "temporarily allow..." apply only to the tab where it was used;
2) Allow the definition of site groups, such as suggested by Foam Head
(independently of the policy groups he suggests). Then, if, say googleapis.com shows up, add a "temporarily allow the google apis group" to the NS menu.
However, looking through this thread, I ran into the suggestion
to support sites defined as "trusted if parent trusted"; if I understand this correctly, if the google API sites are given this trust level, then temporarily allowing a site which uses them, will allow them only in the using site; this solves both my problems, with a simpler user interface.
So -- thanks, and keep up the good work,
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/2009072221 Iceweasel/3.0.14 (Debian-3.0.14-1)