MetaMask / MetaMask/metamask-extension

[Bug]: Confirmations Navigation- Reject All appears in the navigation header when I have a STX Confirmed page with another tx/signature

Open
#30,335 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bugs---Low-Priority INVALID-ISSUE-TEMPLATE regression-prod-12.11.0 regression-prod-12.18.2 Sev3-low 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**

Whenever I have queued 2 tx's (or 1 tx and a singature) if that is a smart transaction, whenever I confirm the STX I can see how the STX confirmation screen is displayed afterwards and I am able to `Reject all` the 2 confirmations, despite the STX one being just informative (no reject possible).

Note: I suspect that's already in prod, but cannot check as STX don't work for me there with Sepolia

**Screenshots/Recordings**

https://github.com/user-attachments/assets/8984c0b3-5531-4e1e-8992-b2dc7c413a0a

**Steps to reproduce**

1. Enable STX
2. Trigger a signature or tx
3. Trigger a tx
4. Confirm the tx
5. See how the navigation displays 2 screens, and Reject all, despite the tx screen being now the STX confirmation/informative page

**Error messages or log output**

```shell

```

**Detection stage**

During release testing

**Version**

12.13.0

**Build type**

None

**Browser**

Chrome

**Operating system**

Linux

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 Chrome on Linux by enabling STX, triggering a signature or transaction followed by another transaction, and confirming it. Inspect the confirmation navigation state after the STX confirmation page appears; done means the informative STX page does not leave an actionable “Reject all” option for the remaining confirmations.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.