For visiting websites, I always use Brave Browser > New Private Window - as my preferred window type.
Thus, when leaving a website and closing the window(s) I had open to that website, the website’s cookies are removed, thanks to how New Private Windows function.
An exception to the windows type that I use, is when using Brave Browser web pages - such as the Settings web pages.
In a Brave Browser > New Window, at:
brave://settings/cookies for example.
A particular workaround for the ‘2-year-old BUG’ has been effective:
In a Brave Browser - New Window, go to:
- Block cookies (aka Cookie blocking):
Visit the cookie-troubled website and set the site-specific Shields (Lion icon) panel setting to UP (aka Shields UP) and the settings to Aggressive/Strict . . . and Cross-site cookies blocked . . . and then open a New Window to
brave://settings/cookies and try the Trash can, for the respective Cookies source.
By the way, as a practice, I do not set a Shields DOWN condition, though many other users of Brave Browser do, and Brave Support suggests that step.
I believe, that the user should TEST, Shields settings changes, one increment at-a-time.
Because, I view, and treat, Brave Browser Shields as a firewall. And, as a firewall in effect, important to gradually open what is necessary per webpage / per website - instead of summarily disabling the firewall.
Except for a troublesome website, I have the GLOBAL Shields settings always set to Aggressive/Strict.
Yet, I agree that Brave Browser > Settings must work properly, and sources for cookies, listed at
- Sites that clear cookies when you close them
. . . should be removeable without having to resort to back-peddling workarounds.