mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-24 11:01:41 +01:00
dbd14d796c
On the signature request and transaction confirmation notification pages, the closure of the notification UI implies that the request has been rejected. However, this rejection is being submitted even when the window is closed as a result of the user explicitly confirming or rejecting. In practice, I suspect this has no effect because the transaction, after being explicitly confirmed or rejected, has already been moved out of a pending state. But just in case there is some present or future edge case that might be affected, the `beforeunload` handler is now removed once the user has explicitly made a choice. This mistake was introduced recently in #7333 |
||
|---|---|---|
| .. | ||
| add-token | ||
| confirm-add-suggested-token | ||
| confirm-add-token | ||
| confirm-approve | ||
| confirm-deploy-contract | ||
| confirm-send-ether | ||
| confirm-send-token | ||
| confirm-token-transaction-base | ||
| confirm-transaction | ||
| confirm-transaction-base | ||
| confirm-transaction-switch | ||
| create-account | ||
| first-time-flow | ||
| home | ||
| keychains | ||
| lock | ||
| mobile-sync | ||
| provider-approval | ||
| routes | ||
| send | ||
| settings | ||
| unlock-page | ||
| index.js | ||
| index.scss | ||