-
Notifications
You must be signed in to change notification settings - Fork 411
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
fix: Close transaction modals as soon as the transaction is submitted #3676
Conversation
Branch preview✅ Deploy successful! Storybook: |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
📦 Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! Seven Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. |
Coverage report
Show files with reduced coverage 🔻
Test suite run success1444 tests passing in 199 suites. Report generated by 🧪jest coverage report action from 985ac27 |
Looks like other types of transactions are also affected by this. So far I tried:
In all of these cases the promise is pending until the transaction is executed so the modal never closes. Setting this PR to draft and will investigate further. Edit: Looks like this only happens when using the MetaMask browser extension and it only happens for transactions that we dispatch without an unchecked signer. I opened a support ticket with MetaMask and will follow up once there are more news. In the meantime we could add a workaround on our side to always use an unchecked signer but we need to make sure this is backwards compatible. |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
I've added a new helper |
Could you please rename the PR to reflect what exactly is fixed on the UI level? Without using the word “unchecked signer” because it’s an implementation detail. |
LGTM I tried several types of tx: |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
68a4482
to
985ac27
Compare
What it solves
Resolves #3675
How this PR fixes it
How to test it
This needs to be tested with MetaMask and at least one other wallet thats not affected e.g. Rabby.
We should also make sure it still works when executing transactions with hardware wallets and nested safes.
The following transaction types need to be tested:
The transaction modal should close when the transaction is executed from the wallet.
Checklist