MetaMask / MetaMask/metamask-extension
[Bug]: Notifications settings cannot be reached under settings menu
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Describe the bug
Notification feature seems to have its own settings that the user cannot access within the settings menu. When the user searches settings for Notifications they are taken to Experimental, where there are no notification settings. This is confusing to offer an additional group of settings from the kebab menu, that are not offered within the settings menu along with every other setting.
Expected behavior
Please let a user find these settings under the regular settings menu.
Please also support a user that doesnt want to have to hunt for the setting and instead uses Settings- Search.
Screenshots/Recordings
Steps to reproduce
- Be at wallet view
- Tap 3 dots
- Tap Settings
- Type in search box
notif - Click the search result
- Note the absence of notification settings in the Experimental menu
Error messages or log output
No response
Detection stage
During release testing
Version
12.4.0
Build type
None
Browser
Chrome, Firefox
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue from the wallet view: open the three-dot menu, enter Settings, and search for “notif” to trace the result into Experimental. Done means notification settings are reachable from the regular settings menu and returned by Settings search, rather than directing users to an empty Experimental section.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100