MetaMask / MetaMask/metamask-extension
[Bug]: Cancelled transaction reported as confirmed in popup
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
The popup notification states that a transaction was confirmed when the **cancellation** of the transaction was confirmed. Because this language of "confirmed" is **exactly the opposite** of what the user wanted when they issued the cancellation, it's a negative user experience.
### Steps to reproduce
1. Initiate a transaction that may take a while to get approved.
2. Attempt to cancel the transaction with the MetaMask interface.
3. When the cancellation is eventually confirmed, the user sees a popup that "Transaction ### was confirmed" or similar when it should instead say the transaction was cancelled.
4. The user can click the metamask popup to see the list of transactions, showing that one as "Cancelled" as intended.
### Error messages or log output
_No response_
### Version
10.17.0
### Build type
_No response_
### Browser
Chrome
### Operating system
Windows
### Hardware wallet
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Reproduce the cancellation flow in the MetaMask interface, then trace the popup notification that appears when the cancellation is confirmed. Done means the popup describes the transaction as cancelled while the transaction list continues to show it as Cancelled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100