And we enable cookies for website we want not all
Was removed because it caused webcompat issues, users enabling not relising it broken most of the web.
That’s a really bad excuse for removing privacy-related features from a privacy-centered browser.
2 Likes
Is there any brave://flags option to block all cookies?
I remember option for Agressive fingerprinting protection was removed from settings UI but we could still enable it from flags, I still to this very day, use the agressive fingerprinting protection and all my websites work just fine.
Maybe introduce a flags options to block all cookies (if not already present)
1 Like
I believe we must have put this back in although I can’t find the issue/pull for it. But I still see Block all cookies on both macOS and Win11 systems:
@Mattches @3e1e27ebecea3893c331 and whoever. The difference is global. The global setting for Block All Cookies in Shields is still hidden. But we can activate it on a site by site basis.
Not sure how long they will have the flag available, but we can reactivate global setting via brave://flags
With the default of having it disabled, global settings wouldn’t allow you to choose to block all.
@Bachsau Not really. Blocking cookies does absolutely nothing for privacy. It stops tracking cookies in terms of them tracking cross-site. The cookies it allows would just be the ones that have your personal preferences for that website. So detectable by that website, only when you visit their website. And you can use things like Forget me when I close this site in order to purge that when you leave, which would allow all content to work but also purge anything saved in your browser.
Completely blocking them just means you’re preventing a lot of things from working. There’s no real benefit and it comes with only potential problems.
1 Like
@Saoiray Ah thank you – thought this thread was referring to Shields panel which is why I was confused.
I also wouldn’t use it for all the reasons mentioned, just didn’t see a reason to remove it. However, it seems to be redundant anyway, as there’s also the website data settings in “Website and protection settings” which can be set to disallow sites from saving any data on the device, including cookies. I haven’t set this globally either, but for a few sites to keep them from misbehaving. It also keeps Brave from sending global domain cookies to subdomains on this list, so they don’t realize you’re logged in on the main site. 