[Bug]: Unexpected popup behavior when interacting with dapps

[sleepytanya]

Describe the bug

Popup functionality seems working not as expected.

Scenarios:

1. Have unapproved transaction

2. Request to switch network - number on the MM icon will increase +1

3. Popup appears but you can't see the network request, only the unapproved transaction

4. If you access the popup manually it will show the unapproved transaction

5. After unapproved transactions rejected, network request can be seen

6. If you go to the MM home page and reject unapproved tx from there the network request will be shown in full screen mode

7. Switch network, do not approve

8. Go to another dapp

9. Start transaction

10. MM icon number will increase +1

11. Popup appears but shows only network request

12. If you access the popup manually it will show the unapproved transaction request

13. After unapproved transactions rejected, network request can be seen

14. If you go to the MM home page and reject unapproved tx from there the network request will be shown in full screen mode

Related issues:

#25361

#25397

Slack discussion links:

https://consensys.slack.com/archives/C03ETQA9EPK/p1695933147044299

https://consensys.slack.com/archives/C03ETQA9EPK/p1695932531166009

Expected behavior

Screenshots/Recordings

popup.mov

Screen.Recording.2024-06-17.at.15.34.40.mov

Steps to reproduce

In the description^^

Error messages or log output

No response

Version

11.16.11

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

[hesterbruikman]

@bschorchit it looks like this issue might describes expected behavior around confirmations sequencing that is not obvious from the UI. Knowing the evolution of confirmation designs, can you take a look please and share if you see it likely this issue can be addressed with a UI improvement? cc @sleepytanya

[bschorchit]

I've assigned this to confirmations @hesterbruikman

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.