-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Disabling Brave Wallet does not remove it from the main menu #31651
Comments
Shame this didn't get any traction. I tried Brave for the first time in a couple of years today. Once again, it's the impossible-to-truly-disable crypto baggage that scared me off. I found this while searching for a solution for the menu problem. |
I am also trying to remove the wallet entry but it seems its hardcoded as i disabled everything in brave://flags that had wallet in name and description |
They can be disabled using policies. A brave article lists some of them: They are written in
If anyone happens to be using NixOS this is quite easy with the This is how settings look afterwards: It would be nice if more could be removed like Web3, Brave Talk and Brave News. Ideally it would have been better if the privacy of Chromium was improved (or some other fork like ungoogled-chromium) to be on par with Brave itself as reported by the Brave employee who created the tests https://github.com/privacytests/privacytests.org (and results here https://privacytests.org/) but without the Brave additions, for those that do not need them. |
Description
Unlike VPN and Sync, disabling the Wallet using
brave://flags/#native-brave-wallet
will not remove it from the main menu.Steps to Reproduce
brave://flags/#native-brave-wallet
Actual result:
Expected result:
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
1.52.130 Chromium: 114.0.5735.198 (Official Build) (64-bit)
c3029382d11c5f499e4fc317353a43d411a5ce1c-refs/branch-heads/5735@{#1394}
Version/Channel Information:
Other Additional Information:
The text was updated successfully, but these errors were encountered: