Open mshakeg opened 1 week ago
I briefly looked into it, and this seems to be an inherent feature of onboard.js and is not configurable on our side. This might change with the new Metamask onboard module (#3841).
Update: #3946 does solve this. ✅
@katspaugh thanks for looking it to it, but why does the Uniswap web ui not have this issue?
They use a different wallet connector library. Like I said #3946 fixes it, so please feel free to follow that.
Bug description
When clicking the "Disconnect" button on the Safe Global web UI, the account does not fully disconnect. Instead, it only clears the connected account from the UI. Upon attempting to reconnect via MetaMask, the previously disconnected account immediately shows up without prompting MetaMask to select an account, leading to a poor user experience.
Environment
Steps to reproduce
Expected result
Clicking the "Disconnect" button should fully disconnect the account from the UI. Upon attempting to reconnect, MetaMask should prompt the user with the "Connect with MetaMask" popup, allowing the user to reselect the account(s) to connect to Safe Global.
The Uniswap web UI at https://app.uniswap.org provides a good working example of this desired behavior. When clicking "Disconnect," it fully disconnects the account on the UI. Upon reconnection, MetaMask prompts the "Connect with MetaMask" popup, enabling the user to select the account(s) to connect.
Obtained result
Clicking the "Disconnect" button only clears the connected account from the UI. When attempting to reconnect via MetaMask, the previously disconnected account immediately appears without the MetaMask prompt, requiring the user to manually delete
app.safe.global
from MetaMask's connected sites list to reconnect a different account.