- Edited
It could be tested to see if it works. I consider it a better solution... as long as it works 
See also this: https://orionfeedback.org/d/1918-allow-custom-filter-lists-for-the-native-adblocker
60
Allow custom filter lists for the native adblocker
Merged 6 posts from I don't care about cookies extension doesn't work.
https://addons.mozilla.org/en-GB/firefox/addon/consent-o-matic/
https://chrome.google.com/webstore/detail/consent-popup-blocker/onnimgmpopjkpbnmnjgcfkndeefgkkig
Both of these seem to work. The former has the performance issues we discussed and made a separate bug tracker for.
Firefox are also working on something that may be useful or of interest - https://github.com/mozilla/cookie-banner-rules-list
Brave seems to be using the easy-cookie list.
This surfaced as well https://www.super-agent.com
There seems to be a subtle difference between blocking cookie notices and approving them.
For the case I can see on your picture I use "Make ReCaptcha's "I'm not a robot" accurate" Firefox extension. Of course I can't guarantee it would work on Orion. https://addons.mozilla.org/en-US/firefox/addon/make-recaptcha-text-accurate/
I still don't care about cookies was intended (as far as I see it) for removing banners at the bottom of the webpage that claims that it uses cookies.
6 months later
Any update on when this will ship @Vlad ? Orion blocks cookie consent dialogs by default so having the ability to customise filter lists would prevent that behaviour (I know this has been discussed before).
Anatomy5803 Planned for 126
24 days later
Vlad Vivaldi on iOS has an extremely slick implementation of this. I think Orion could just copy it.
12 days later
Would this support blocking visual (DOM) elements as well, or just network blocking?
This is a thread just for custom block lists. We will plan to have this for 127.
- Edited
Vlad I'm asking because some of these filter lists also contain DOM filtering rules, for example:
play.google.com#@#div[aria-label="Ads"]https://github.com/easylist/easylist/blob/master/easylist/easylist_allowlist_general_hide.txt
I'm not sure if this is something Orion already supports or not because the current content blocking implementation is kind of a black box to me. But allowing configurable lists would allow adding some of these rules, so I'm wondering if this will work out of the box, or is it a separate feature.
Is a custom whitelist/allowlist also planned as part of this implementation?
Brief Summary
I propose that Orion not block cookie consent dialogues by default. Instead, there should be an opt-in setting for users who want to enable this feature.
Details:
I propose that Orion Browser should change its default behavior so that cookie consent dialogues are no longer blocked by default. Instead, there should be an opt-in setting for users who want to enable this feature. This would give users more control over their privacy and would make it easier for them to make informed choices about the cookies that are stored on their devices.
Other ad blockers, such as Brave's ad blocker, uBlock Origin, and AdGuard already allow users to choose whether or not to block cookie consent dialogues. This is a common feature in ad blockers, and I believe that Orion Browser should also offer it.
Merged 2 posts from Don't block all cookie consent popups by default.
We are moving to fully customizable block list, hopefully for 126! Should be in RC next week.
8 days later
5 days later
- Edited
@Vlad This addition is fantastic, really excited to have this in Orion and I think I can actually get rid of uBlock Origin now! Some feedback from my side: It would be nice if we were also able to enter blocking rules (e.g. ##img.some-ad) manually. A simple textarea under custom blocking lists would do. If you want to add a custom rule right now you have to actually host the rule file somewhere which is kind of inconvenient.
Is this something worth opening a new feature request thread for?
11 days later
No one is typing