fix: do not default to mm provider when toggle is off #1079
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes BX-1088
Figma link (if any):
What changed (plus any additional context for devs)
now:
when our default rnbw provider toggle is off and the user has metamask, we're relaying requests to mm provider
this was probably causing the issue, users had the tooggle off, eip6963 was picking rainbow correctly but we were relaying requests to mm
with this pr:
when our default rnbw provider toggle is off and the user has metamask we're still using rainbow provider if the dapp pick the rainbow provider
this won't affect the window.ethereum override when the rnbw by default tooggle is on since that logic is happening on
inpage
Screen recordings / screenshots
What to test