Issue 44114 chrome support for the browser namespace#44149
Open
rebloor wants to merge 2 commits into
Open
Conversation
Contributor
|
This pull request has merge conflicts that must be resolved before it can be merged. |
rebloor
changed the base branch from
Issue-44114-Chrome-support-for-the-browser-namespace
to
main
Member
|
By the way, the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update various content to note that, with the exception of extensions using DevTools pages, browsers based on Chromium 148 support the
browsernamespace for the WebExtension APIs.Motivation
To provide up-to-date information on Chrome's browser namespace support.
Related issues and pull requests
Fixes #44114
Changes for Extension Workshop in mozilla/extension-workshop#2336
See also #44225