Skip to content
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

Dropdown close (not open on connect) #349

Closed
MarioProjects opened this issue Mar 8, 2022 · 6 comments
Closed

Dropdown close (not open on connect) #349

MarioProjects opened this issue Mar 8, 2022 · 6 comments

Comments

@MarioProjects
Copy link

Hello!

First of all thanks for your amazing work. I am integrating the wallet adapter and facing some strange, at least for me, behavior. When the user connects the wallet, the dropdown opens instantaneously before. There is an option to close it or even better not open it? Screenshot: https://ibb.co/Xtgb9Q2

Thanks again!

@jordaaash
Copy link
Collaborator

Hmm, I'm not sure I understand what's happening. Can you describe the exact actions taken and what happens as a sequence in a numbered list?

@MarioProjects
Copy link
Author

Sure, I will try :)

  1. I follow the Next.js config steps with exactly the same steps described in the main README.
  2. Connect my wallet with a WalletMultiButton component.
  3. The wallet connects and the button modifies with the wallet info (wallet logo, in this case, Phantom, and the short version of wallet address)
  4. The wallet button dropdown opens with the options of the -> Copy Address, Change wallet, Disconnect.
  5. I got back the control of the application (we could say).

The problem is step 4. I don't know why that dropdown, as shown in the screenshot (https://ibb.co/Xtgb9Q2), is opening "alone". Could we manage to don't auto-open?

@jordaaash
Copy link
Collaborator

I'm afraid I haven't seen this happen before. Could you link to a repo that contains the code that produces the issue? I'll try to test it out directly and see if I can find out what's going on.

@jordaaash
Copy link
Collaborator

The screenshots shown indicate that there are customizations made to the application. Closing as I can't reproduce this in the example starter project.

@plasmare
Copy link

plasmare commented Apr 14, 2022

Also having this issue without any customisations

@shadeglare
Copy link

The strange behaviour still exists. To reproduce it you have to activate the auto-connect property in the demo example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants