RequestPolicy is a Firefox extension that gives you control over cross-site requests. --- Be sure to look at the dev-1.0 branch as that's where all of the interesting work is happening. See also: https://www.requestpolicy.com/1.0.html
Firstly, I also use NoScript and particularly like several things that they have done that works well. One thing I've noticed is some sites may have a lot of cross-site requests, but never too many for it to run off the screen. With how NoScript has scrips displayed, they have "Allow this script," and "Temporarily allow this script," which works nicely, because there are only two options to choose from, but for yours, you have four options to choose from, which will make the list very long if they weren't hidden inside a nested drop-down menu. Now, to the point, I often have a good idea of which cross-site requests I will likely need to allow to see what I want to see on the webpage, however the page is reloaded after every request is allowed. For Amazon cloud hosting sites, some pages may have 10 to 12 that we need to set to allow, reloading after each individual one takes quite a while actually. I have a suggestion:
1) Similar to NoScript, where hovering over the icon has a different behavior than if the icon was clicked, if the icon is hovered over, refresh the page when any one destination is allowed. If the icon is clicked, keep the dropdown window open until we click anywhere outside the boundaries of the addon. With the latter, this way we can set multiple destinations, click off to the screen and let it reload the page with those multiple destinations allowed.
2) I was wondering about just adding a middle click and a right click on a destination to have different behaviors. A middle-click will entail allowing the the site to access the destination; and a right-click will allow all sites access to the destination.
Those are my two ideas. Also, I think I may have found something where the expected behavior doesn't happen.
When I put, say, cloudfront.net as a whitelisted destination it doesn't whitelist any subdomains from that domain, which I understand, because the request isn't to "cloudfront.net," but to "subdomain.cloudfront.net." But then I tried perhaps regex or a boolean by adding a "." or an asterisk to the beginning of it, like, ".cloudfrount.net," however this does not work as expected.
Firstly, I also use NoScript and particularly like several things that they have done that works well. One thing I've noticed is some sites may have a lot of cross-site requests, but never too many for it to run off the screen. With how NoScript has scrips displayed, they have "Allow this script," and "Temporarily allow this script," which works nicely, because there are only two options to choose from, but for yours, you have four options to choose from, which will make the list very long if they weren't hidden inside a nested drop-down menu. Now, to the point, I often have a good idea of which cross-site requests I will likely need to allow to see what I want to see on the webpage, however the page is reloaded after every request is allowed. For Amazon cloud hosting sites, some pages may have 10 to 12 that we need to set to allow, reloading after each individual one takes quite a while actually. I have a suggestion:
1) Similar to NoScript, where hovering over the icon has a different behavior than if the icon was clicked, if the icon is hovered over, refresh the page when any one destination is allowed. If the icon is clicked, keep the dropdown window open until we click anywhere outside the boundaries of the addon. With the latter, this way we can set multiple destinations, click off to the screen and let it reload the page with those multiple destinations allowed.
2) I was wondering about just adding a middle click and a right click on a destination to have different behaviors. A middle-click will entail allowing the the site to access the destination; and a right-click will allow all sites access to the destination.
Those are my two ideas. Also, I think I may have found something where the expected behavior doesn't happen.
When I put, say, cloudfront.net as a whitelisted destination it doesn't whitelist any subdomains from that domain, which I understand, because the request isn't to "cloudfront.net," but to "subdomain.cloudfront.net." But then I tried perhaps regex or a boolean by adding a "." or an asterisk to the beginning of it, like, ".cloudfrount.net," however this does not work as expected.