Do blocklists have to be all-or-nothing? That is, if we have a site that breaks under “shields-up” but works fine on “shields-down”, and I decide that ONE (or more, I suppose) normally blocked element is an acceptable risk FOR THAT SITE, I seem to be missing any way to toggle it (and keep the rest of the blocks enforced and in place).
I am not looking to call it a “bug” or a change to all users of Brave, nor enable a particular thing worldwide, just one item on one site.
Brave version: Version 1.52.126 Chromium: 114.0.5735.133 (Official Build) (64-bit) (Linux)
You can’t disable Default lists, so yes, it is all or nothing since you would have to disable the adblocking or shields.
You can create exceptions to Network filtering rules, so do that instead if necessary/possible.
Why do you want to do it though, your don’t explain why you would want to disable lists per site, either the site, the only reason you state is 'if a site breaks", I mean, if a site broke because of shields, report it with the adblocking category explaining the problem with screenshots or not, like if there is a adblocking detection based on blocking some script, and if not, well, then it doesn’t matter, because it is not breaking anything.
I mean, not even uBlock allows you to do what you are asking for, you either disable the whole adblocking per site or individual lists from all sites.
If you are asking these questions, well, I doubt you will know what you are doing to ‘unbreak sites by disabling individual lists’, if you aren’t already creating exceptions or making your own custom filters to fix problems, then seems like you should just report it and let the people like FanboyNZ to handle it, he works at Brave and also maintains Easylist and Fanboy lists and he knows people around that work in other lists I guess to make sure all default lists work okay.
First thanks for confirming that I am not missing something. That’s really the question, and further props for the quick response!
To your other points: prior to making Brave my primary browser, I was a Palemoon man, and while I had adblock addons, my favorite tool was RequestPolicy - it was very easy to toggle what was getting blocked on a per-site basis. You could define a rule as origin, destination, or origin+destination; the latter being perfect for my use case.
I can play with the network filtering rules, if you are saying that’s the means of doing so in Brave’s world. I’ve been lucky enough and grateful enough things “just work” on any site worth dealing with with Brave.
If you want a specific example, go to Open Farm Petfood, pick a product, and try to add to cart. With shields up, nothing happens. If you disable shields, it will add. Looking at what is being blocked, I’m going to guess one of the A/B tester companies (like kameleoon) are the offender, and I’d consider allowing them on this website only - while continuing to block all the other trackers, sentries, and garbage. To prove this hypothesis, however, I have to do it one by one (lets exclude binary division for sake of argument). Regardless of the end process - lets say I make my own ad list - Requestpolicy made it really quick to cycle through the combinations to do so, and I was hoping I could do it natively in Brave, too.
Likewise, I’ve had bank site issues - all fixed eventually - but ones where I’d rather turn on one or two potentials rather than shutting off /everything/ until the master list maintainer gets around to updating. I get that things take time, and the maintainers have a lot on their plate- this is an interim measure, hopefully, if used.
