While the logic behind the transactions history is right the UI for cancelling transactions might be confusing to users. One Cancelled transaction is shown on the Activity list as three transactions. Cancellations made In-app and using Custom nonce look different on the Activity list. To provide more clarity for the users it might be reasonable to consolidate cancellation steps in one Cancelled transaction on the Activity list.
Steps to reproduce:
a) In-app cancellation
Send regular Eth transaction
Cancel it using In-app method (Cancel button)
After transaction successfully cancelled Activity list shows three transactions - 1 Cancelled and 2 Receive transactions
Stakeholder review needed before the work gets merged
[ ] Engineering (needed in most cases)
[ ] Design
[ ] Product
[ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
What is this about?
While the logic behind the transactions history is right the UI for cancelling transactions might be confusing to users. One
Cancelled
transaction is shown on theActivity list
as three transactions. Cancellations made In-app and using Custom nonce look different on theActivity list
. To provide more clarity for the users it might be reasonable to consolidate cancellation steps in oneCancelled
transaction on theActivity list
. Steps to reproduce: a) In-app cancellationActivity list
shows three transactions - 1Cancelled
and 2Receive
transactionshttps://github.com/MetaMask/metamask-extension/assets/104780023/8e76b96e-c705-4f08-84e3-c99acaba36dc
b)
Custom nonce
Activity list
- 1Send
and 2Receive
.https://github.com/MetaMask/metamask-extension/assets/104780023/0347abd9-ed5b-4de2-843f-5cce1f1c0bde
MetaMask 11.6.1
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References
No response