From 34e4e226437ce7826a0b02c63eeb8d604b0fc50b Mon Sep 17 00:00:00 2001 From: rebloor Date: Wed, 26 Jun 2024 21:47:16 +1200 Subject: [PATCH] MV3 guide note for fallback for _execute_browser_action (#1886) * Fallback for _execute_browser_action * Suggestions from (MDN content) review --- .../documentation/develop/manifest-v3-migration-guide.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/documentation/develop/manifest-v3-migration-guide.md b/src/content/documentation/develop/manifest-v3-migration-guide.md index 4ae787f7a..c7f88b96d 100644 --- a/src/content/documentation/develop/manifest-v3-migration-guide.md +++ b/src/content/documentation/develop/manifest-v3-migration-guide.md @@ -168,6 +168,10 @@ As the old and new key and API are otherwise identical, the changes needed are r - update API references from `browser.browserAction` to `browser.action`. - if used, change `_execute_browser_action` to `_execute_action` in the `commands` manifest key and in the [`menu.create`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus/create) and [`menu.update`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus/update) API methods (or their aliases `contextMenus.create` and `contextMenus.update`). +::: note +If the user changes the shortcut of the `_execute_browser_action` command, it is automatically carried over to the `_execute_action` command when an extension migrates from Manifest V2 to V3. This was implemented in Chrome 111 and Firefox 127. +::: + ::: note In Chromium and Safari, the Browser Action and Page Action APIs are unified into the Action API, `page_action` is merged into the renamed `action` key, and the `_execute_page_action` special shortcut is replaced by `_execute_action`. Firefox retains the page action API, key, and special shortcut in the developer preview but will merge the page action features into action in a later release. :::