I never want to globally allow cascading permissions to 3rd party scripts, its only when:
- a site i like asks me to disable blocking and i wish to do that this one time
- i can't get a feature of the current page to load, usually a video, and i want to just allow all in order to get it to work
i currently handle these cases by flipping on "allow scripts globally", reload, then try to remember to turn off that setting, and i think noscript can make this both safer and more straightforward.
the feature i'd like to see is one that allows cascading permissions to 3rd party scripts for the current site in the current tab, and perhaps tabs it opens in the same domain from clicked links. the language i'd expect is something like "temporarily allow all on good-site.tld in this tab"
it seems that noscript doesn't currently do anything specific to a tab, does it. i think in several cases it might be what people expect and probably a direction to investigate.
request feature: cascade permissions for this site now
request feature: cascade permissions for this site now
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Firefox/47.0
Re: request feature: cascade permissions for this site now
Cascading permissions is not per-site.
It was implemented at the request of the Tor project, as a way to prevent sites from fingerprinting you by determining the contents of your whitelist.
In general, cascading permissions is not a secure practice, except perhaps when combined with another extension to manage third-party requests, like RequestPolicy or uMatrix.
Perhaps you would be better off creating a second profile where cascading permissions are enabled, and using it only for selected sites?
It was implemented at the request of the Tor project, as a way to prevent sites from fingerprinting you by determining the contents of your whitelist.
In general, cascading permissions is not a secure practice, except perhaps when combined with another extension to manage third-party requests, like RequestPolicy or uMatrix.
Perhaps you would be better off creating a second profile where cascading permissions are enabled, and using it only for selected sites?
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Re: request feature: cascade permissions for this site now
Ditto.i currently handle these cases by flipping on "allow scripts globally", reload, then try to remember to turn off that setting
And that remember part is tough!
Isn't Cascade going to be Safer then Allow Global?noscript can make this both safer
I would think so, I would prefer to use Cascade rather then Allow Global.
+1 for making Cascade more discoverable.and more straightforward
Even something like an option for Cascade to take preference over Allow Global (context-menu shows Cascade rather then Allow Global) & maybe something like holding down Shift toggles its meaning. (Could go either way.)
I'd think that would be harder to implement ? & is more like the requests for Temporarily Allow All (or similar) to only have an effect on the current tab.the feature i'd like to see is one that allows cascading permissions to 3rd party scripts for the current site in the current tab, and perhaps tabs it opens in the same domain from clicked links
Anyhow, in general a +1 from me.
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:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40