-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Desktop] Add Block trackers & ads (aggressive) setting to apply cosmetic filtering to 1p items #8475
Comments
The implementation could be pretty simple:
|
I like even more minimal yet viable MVPs. Per https://twitter.com/myphs/status/1233110060903075844?s=20 what many want is the "uBO me globaly please" setting. That would be a single setting, could even start with brave:flags or better internal URL and no official settings UX. But what would it flip internally? |
Designs for brave://settings added and dropdown option typo fixed. |
Verification passed on
Verified test plan from brave/brave-core#5481 Verified aggressive setting in Brave Shields Panel works: Verified allowing all trackers and ads in Brave Shields works as expected Verified allowing all trackers and ads in Verified passed using
Verification passed on
Verified default setting in When sites shield settings are set to When sites shield settings are set to When site shield settings are set to When global shield setting for When global shield setting for When global shield setting for |
Description
by default we have cosmetic filtering that attempts to differentiate 1p and 3p ads, and only block the latter.
Some users would like to do the simpler, "apply all cosmetic filters, always" approach. Basically, just do what uBO does.
This issue would be to modify the current cosmetic filtering to have an option to automatically inject all cosmetic filters, and not do party checks. '
Design
Shields panel
brave://settings
Figma for CSS, layout, sizing: https://www.figma.com/file/3A6F6VrxVahiZFxLr7j7FO/Desktop-Brave-Shields?node-id=16%3A14877
The text was updated successfully, but these errors were encountered: