Page 1 of 1

request feature: cascade permissions for this site now

Posted: Sun Mar 27, 2016 6:43 pm
by jpmh
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.

Re: request feature: cascade permissions for this site now

Posted: Tue Mar 29, 2016 4:44 am
by Thrawn
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?

Re: request feature: cascade permissions for this site now

Posted: Wed Mar 30, 2016 12:29 am
by therube
i currently handle these cases by flipping on "allow scripts globally", reload, then try to remember to turn off that setting
Ditto.
And that remember part is tough!
noscript can make this both safer
Isn't Cascade going to be Safer then Allow Global?
I would think so, I would prefer to use Cascade rather then Allow Global.
and more straightforward
+1 for making Cascade more discoverable.
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.)
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
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.

Anyhow, in general a +1 from me.