Exception rules in brave://adblock or regional lists are ignored
See original GitHub issueCurrently exception rules added in brave://adblock and in regional lists are ignored, because of how filter logic is applied (main set of rules is queried, then regional, then custom, in order, until one of them has a match). This means an exception in a later list won’t correctly except a rule from a previous set, and that important
wont override an exception from a previous set.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Brave Adblock Filter, block element, ads and privacy setting
Currently exception rules added in brave://adblock and in regional lists are ignored, because of how filter logic is applied (main set.
Read more >How do I turn off just *part* of the Brave shields for a specific ...
Currently exception rules added in brave://adblock and in regional lists are ignored, because of how filter logic is applied (main set.
Read more >Brave does not update custom filter lists - Ad-Blocking
As title says, while Brave checks for updates to the built-in lists (global and regional) every few hours, it does not check for...
Read more >How to turn off ad blockers - Brave Browser
In this article, we'll explain how ad blockers work, and how to disable ad blocker on various devices and operating systems. How ad...
Read more >SugarCoat: Programmatically Generating Privacy-Preserving ...
filter lists published by EasyList, EasyPrivacy, and uBlock Origin include more than 6,000 exception rules to unblock compatibility-.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
the last I know of this is a conversation with @antonok-edm where we discussed a couple of approaches and their trade-offs and agreed that he’d post it up for discussion
@antonok-edm isn’t currently working on this, so we’ll need to figure out internally whats best here.
I believe @bbondy and @AndriusA had a plan for tagging rules so that they could all be part of a single engine, of having the layered engines (which is what causes the issue). When either of you have a chance, could you say if the above (tag the rules) approach is still the official plan of action, and if so, if anyone is currently working on it (or if its in the backlog)?