Skip to content
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

MV3 guide note for fallback for _execute_browser_action #1886

Merged
merged 2 commits into from
Jun 26, 2024

Conversation

rebloor
Copy link
Collaborator

@rebloor rebloor commented Jun 12, 2024

Description

Addresses the documentation needed for Bug 1797811 Migrate user-defined shortcuts from _execute_browser_action to _execute_action, by adding a note to the Manifest v3 migration guide.

Related issues and pull requests

Related update to MDN mdn/content#34091

@rebloor rebloor requested a review from dotproto June 12, 2024 23:15
@rebloor rebloor self-assigned this Jun 12, 2024
@rebloor rebloor changed the title Fallback for _execute_browser_action MV3 guide note for fallback for _execute_browser_action Jun 12, 2024
@rebloor rebloor requested a review from Rob--W June 25, 2024 02:47
::: 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
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.

We are keeping them both. Please create a new PR with this suggested change and I will confirm with my team whether we should update the docs as I suggested.

@rebloor rebloor merged commit 34e4e22 into mozilla:master Jun 26, 2024
1 check passed
@rebloor rebloor deleted the fallback-for-_execute_browser_action branch June 26, 2024 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants