MetaMask / MetaMask/metamask-extension
[Bug]: Discover does not take to the corresponding network selected
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
Discover does not take to the corresponding network selected
### Expected behavior
Network selected should navigate to the corresponding Discover network.
### Screenshots/Recordings
https://github.com/user-attachments/assets/5b4c20fa-4ceb-40c2-b880-386703fa4407
### Steps to reproduce
1. Network picker → network list
2. Find Linea or Solana
3. Open overflow menu → Discover
4. Confirm it opens something like:
https://app.metamask.io/explore/networks/linea (or /solana)
### Error messages or log output
```shell
```
### Where was this bug found?
Internal release testing
### Version
13.44.0
### Build type
None
### Browser
Chrome
### Operating system
MacOS
### Hardware wallet
_No response_
### Additional context
_No response_
### Severity
_No response_
Contributor guide
Research direction
Start at the network picker and its overflow-menu Discover action, then trace how the selected network is passed into the Discover destination. Reproduce with Linea or Solana in Chrome on macOS and verify that Discover opens the corresponding network URL, such as /explore/networks/linea or /solana.
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
- 64/100