-
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
Revise the behavior of "Extensions (Brave Wallet fallback)" setting #29853
Comments
Extensions (BW fallback) will still be default value with the following exceptions:
|
Assigned to @cypt4. |
Just noting that we'll also remove the ability for web3 apps to query public blockchain when the wallet is not created by doing this. I think this is ok, but I just wanted to note that the scope of the change goes beyond not prompting the user to setup a wallet when a dapp tries to ask for permission. |
…18172) * Disable brave wallet script injection if wallet is not created or MM is installed Resolves brave/brave-browser#29853
@jamesmudgett @cypt4 @yrliou set the above as |
@kjozwiak Thanks, yes it should be QA/Yes. |
The above requires |
Moving this into |
Verification passed on
29853.mp4 |
There are reports that Brave Wallet fallback setting "Extensions" is interfering with MM. The goal here is to detect the MM extension and avoid inserting BW as a fallback handler when the setting "Extensions" (soon to be renamed "Extensions (Brave Wallet fallback)") is enabled
For setting Extensions(BW fallback), we will only provide fallback when MM is not installed and wallet is not created.
The text was updated successfully, but these errors were encountered: