MetaMask / MetaMask/metamask-extension

[Bug]: Perps add funds confirmation flow has fee visibility and cancel-routing issues

Open
#41,252 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

regression-RC-13.25.0 Sev2-normal team-confirmations type-bug
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

Describe the bug

Perps add-funds confirmation flow shows two problems: fee is 0 (is that right?), and cancel action routes the user to Activity instead of returning to the originating funding context.

Expected behavior
  1. Confirmation should show the expected MetaMask fee information when applicable.
  2. Cancel should return users to the previous funding context and preserve flow continuity.
Screenshots/Recordings

N/A

Steps to reproduce
  1. Open MetaMask Extension in the EXP build.
  2. Enter Perps and start Add funds flow.
  3. Reach the confirmation step.
  4. Review fee section.
  5. Click Cancel.
  6. Observe routing and flow destination.
Error messages or log output

N/A

Where was this bug found?

Internal release testing

Version

13.25.0 EXP March 25

Build type

Other (please specify exactly where you obtained this build in "Additional Context" section)

Browser

Chrome

Operating system

MacOS

Hardware wallet

N/A

Additional context

Found during internal PERPS release testing.

Severity

To be added by internal support / PM.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the flow in the EXP build by opening Perps, starting Add funds, and reaching confirmation. Inspect the confirmation fee section and the Cancel route; done means applicable MetaMask fee information is shown and Cancel returns to the originating funding context while preserving flow continuity.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.