I was reading a few feature requests related to more granular script blocking exceptions (essentially, rather than allowing all scripts on a site allowing certain scripts on a site and having Shields remember that setting across browsing sessions):
Scripts are only allowed once. Why not remember it like device recog and cookie settings?
Remember blocked scripts for a site
I like the ideas above but wonder if that will result in a large amount of data storage or cumbersome custom saved settings area within the browser depending how many sites are visited and have custom script blocking/allowance settings.
However, I wonder if people are more interested in blocking a certain set of scripts across all sites. For example, they want to block any ajax.googleapis.com script on any site they visit. Maybe, rather than having a site-by-site granular set of allowed scripts, it would be cleaner and easier to have a script “blacklist” in Brave Shields that tells shields to continue blocking those scripts regardless if you disable shields script blocking for that site.
- The block only would block scripts for that individual site (e.g. if i added “ajax.googleapis.com” to the block list, all scripts would be blocked if I navigated to ajax.googleapis.com but if I went to a different site (with scripts allowed) ajax.googleapis.com scripts would still run.
So if it is a set of scripts that you want to block across all sites, it seems like a blacklist (that is coded to take precedence over shield script block exceptions) would be a better/cleaner way to go.
What do you think @sleepy62 @TheScrubbyForest @jaybird @mangobe553?