You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stop blocking display of transaction approval window on resolution of ppom security alert response (#22778)
## **Description**
Solves this problem:
For people on slow networks, the amount of time it takes from "Dapp
button click" -> "Popup notification window appears" might be a problem.
When blockaid is toggled off, and the network is throttled to slow via
the chrome dev tools, I see a ~3 second worse case for this time, but
when blockaid is toggled on, I see a 12 second (or even a bit longer)
worst case scenario for this time.
The risk here is that users unexpectedly see a longer delay then usual,
and so think they need to click the button again, and then get shown
multiple confirmation requests and confirm all of them, leading to fund
loss.
This can happen on either slow internet connections, or if an infura
request is taking longer than usual (which could effect people
regardless of internet connection). Yesterday when I first saw this
issue, I wasn't slowing down my connection, but it still took ~20
seconds to open. Probably a somewhat rare case (because as I mentioned I
didn't notice any problems again until I intentionally throttled the
network requests), but even if it only affected 10% of users only once a
month, that would be enough to get plenty of "why did metamask just take
20 seconds to open a confirmation window?!?" complaints.
<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
## **Related issues**
Fixes:
## **Manual testing steps**
1. Go to this page...
2.
3.
## **Screenshots/Recordings**
<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->
### **Before**
<!-- [screenshots/recordings] -->
### **After**
<!-- [screenshots/recordings] -->
## **Pre-merge author checklist**
- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've clearly explained what problem this PR is solving and how it
is solved.
- [ ] I've linked related issues
- [ ] I've included manual testing steps
- [ ] I've included screenshots/recordings if applicable
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.
- [ ] I’ve properly set the pull request status:
- [ ] In case it's not yet "ready for review", I've set it to "draft".
- [ ] In case it's "ready for review", I've changed it from "draft" to
"non-draft".
## **Pre-merge reviewer checklist**
- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
0 commit comments