-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unhandled options #1
Comments
For network filters, there are still a few rule options that are not supported, wrt brave-experiments/ad-block#217
|
See also - brave/brave-browser#8478 |
I noticed uBlock have added some new features like Some of these features might not seem too relevant or used even today, but since Brave uses uBlock lists as default they are important to support, because when you put all the unsupported rules together, they represent an important amount of rules Brave is currently ignoring, which obviously reduce the potential of Brave to reduce tracking and avoid bad popups and all that in many websites.
❌= Not supported ❌ |
A few options are not currently handled from easylist and easyprivacy:
popup
- Include pages opened in a new tab or windowgenerichide
- Used to prevent applying global element rules on a page (e.g.@@||example.com^$generichide
)document
- Used to whitelist the page itself (e.g.@@||example.com^$document
)webrtc
- Include or exclude connections opened via RTCPeerConnection instances to ICE serverselemhide
- Used to prevent element rules from applying on a page (e.g.@@||example.com^$elemhide
)genericblock
- Used to prevent applying global blocking rules on a page (e.g.@@||example.com^$genericblock
)The text was updated successfully, but these errors were encountered: