-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[Bug]: Initiating a Send transaction from the Tokens tab occasionally requires two or more clicks on the 'Send' button to successfully start the transaction #24925
Comments
Also present on doubleClick.mov |
The issue is still present on the latest build Slack discussion link: |
Holding off on this one for now since it's seems to be related to the broader |
This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions. |
This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions. |
I no longer see this issue, tested on RC 12.10.0. Leaving as closed |
Describe the bug
Initiating a Send transaction from the Tokens tab, specifically when selecting a token, occasionally requires two or more clicks on the 'Send' button to successfully start the transaction.
Expected behavior
Screenshots/Recordings
Chrome:
https://jam.dev/c/b04375a9-b789-4c5b-807e-262b353f4149
Firefox:
doubleClickTokenTab.mov
Steps to reproduce
Error messages or log output
Version
dev build
Build type
None
Browser
Chrome, Firefox
Operating system
MacOS
Hardware wallet
No response
Additional context
dev build 4c64f44
Severity
No response
The text was updated successfully, but these errors were encountered: