-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Bug]: Keyboard shortcut (Alt+Shift+M) broken on Chrome #31837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Labels
regression-prod-11.16.7
Regression bug that was found in production in release 11.16.7
Sev2-normal
Normal severity; minor loss of service or inconvenience.
team-extension-platform
Extension Platform team
type-bug
Something isn't working
Comments
7 tasks
Please assign this to me |
7 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 14, 2025
<!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** </tbody><!--EndFragment--> </body> </html> "_execute_browser_action" is no longer available in Chrome MV3, should use "_execute_action". but "_execute_action" doesn't work in Firefox(Firefox MV3 only support "_execute_browser_action" now). **Solution**: Add both "_execute_browser_action" and "_execute_action" in config file <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> [](https://codespaces.new/MetaMask/metamask-extension/pull/31844?quickstart=1) ## **Related issues** Fixes: #31837 ## **Manual testing steps** 1. Install the extension in Chrome 2. Open Chrome and type Alt+Shift+M 3. Check if popup opend ## **Screenshots/Recordings** ### **After** Test in Chrome: https://github.com/user-attachments/assets/7bfc858f-7da1-4931-b100-c44e28dfee93 Test in Firefox: https://github.com/user-attachments/assets/32d6e330-c226-49b6-ae40-41ece5e509dd <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
Hi @HowardBraham , thank you for your suggestions.
brave.mp4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
regression-prod-11.16.7
Regression bug that was found in production in release 11.16.7
Sev2-normal
Normal severity; minor loss of service or inconvenience.
team-extension-platform
Extension Platform team
type-bug
Something isn't working
Describe the bug
The keyboard shortcut for opening MetaMask is broken on Chrome, ever since the migration to MV3.
Expected behavior
Alt+Shift+M should open the browser-action popup.
Screenshots/Recordings
No response
Steps to reproduce
Install the extension in Chrome, and type Alt+Shift+M
Error messages or log output
Detection stage
In production (default)
Version
11.16.7
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
The text was updated successfully, but these errors were encountered: