Every page I go to, i seems that I can 'temporarily allow' w or x site, and then there is a chain-reaction... where now I am asked to approve/allow site y, then z, then aa, etc...
It would be useful to see the 'chain' of what is calling what..
ie
I allow xyzzy.com ---> page reloads ---> now I am asked to approve site 'a' --> I approve ----> I am asked to approve site 'b' .. etc
What is needed is twofold:
a) A mechanism in which the script-chain can be followed, without executing the scripts, and a list of domain-names that would have been called for script-execution, is compiled and presented. (would require script-analysis and a 'meta-scripted' DNS-lookup / -crawl.)
*or* the script-chain can be followed, 'virtually' executing the scripts in a sandbox... and a report is generated on the actual text of what script-text "would have been" executed.
What script just triggered ?
What script just triggered ?
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9
- Giorgio Maone
- Site Admin
- Posts: 9524
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: What script just triggered ?
It seems overly complicated, unless you really need it for analysis purposes.
On the other end, if it's only for convenience's sake (avoiding to reopen the menu multiple times), you set the noscript.stickyUI.liveReload about:config preference to "true": automatic reload will happen on each permission change, but the menu will be kept opened until you move away.
On the other end, if it's only for convenience's sake (avoiding to reopen the menu multiple times), you set the noscript.stickyUI.liveReload about:config preference to "true": automatic reload will happen on each permission change, but the menu will be kept opened until you move away.
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9