-
Notifications
You must be signed in to change notification settings - Fork 4
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
Connect wallet without Taho extension installed #381
Comments
Pasting @Shadowfiend's comment from a duplicated #388 issue here:
|
@Shadowfiend , should we show that “Download Taho” for all users, even those who already have Taho installed? Or only those without it? |
That should specifically be for users who don't have Taho installed (this should be pretty easy to detect, EDIT to say: just saw that we already make Connect wallet redirect to the Chrome store if no wallet is installed—hooking into that if there are wallets installed but none of them is Taho is also fine tbh, but then maybe we should say “Connect Taho”? Let's hook into the existing functionality though and then can discuss in product whether we want to tweak. |
I think that this redirect does not always work - it didn't work for me yesterday (see #389). Jagoda told me that whether the Chrome Store is opened or not is decided by an external component. So I think it would be good to have somewhere on the page a link to Taho extension app. |
ugh, I missed comments from this issue in the gh notifications 😬 will take a look at that first thing tomorrow |
Closes # #381 ### What There is a issue related to incorrect handling of the Taho wallet in the `@web3-onboard/taho` library. Let's fix this with a patch file. The solution is still not ideal because it does not catch the change of which wallet is switched on. This means that when we install the Taho wallet we have to refresh the page to see that the wallet has been installed. I think this solution is enough at the moment. Let's solve this problem in #423. ### Testing **When MetaMask is installed** - [ ] Try connecting when the wallet is the default - [ ] Try connecting when the wallet is not the default **When MetaMask is'n installed** - [ ] Try connecting when the wallet is the default - [ ] Try connecting when the wallet is not the default **When Taho isn't installed but MetaMask it is** - [ ] There is no connection possible. The user receives the correct message.
Done in #422 |
There are wallet connect scenarios that aren't working as we'd like.
When I have MetaMask installed but not Taho, if I click Connect wallet, I see an error:
Screen.Recording.2023-10-16.at.9.57.57.AM.mov
I think ideally, we'd like to do that same as this scenario below:
When I don't have Taho or MetaMask wallet installed, if I click Connect Wallet from the portal landing page, it redirects me to the Chrome store to install Taho
Screen.Recording.2023-10-16.at.9.57.30.AM.mov
I'm not sure that either really matters for beta since you shouldn't really know about this unless you have a Taho wallet. But, this is something we saw in a meeting earlier while we were looking at the beta site and we wanted to log it.
The text was updated successfully, but these errors were encountered: