Skip to content

Issue 44114 Chrome support for the browser namespace#2336

Open
rebloor wants to merge 4 commits into
mozilla:masterfrom
rebloor:Issue-44114-chrome-support-for-the-browser-namespace
Open

Issue 44114 Chrome support for the browser namespace#2336
rebloor wants to merge 4 commits into
mozilla:masterfrom
rebloor:Issue-44114-chrome-support-for-the-browser-namespace

Conversation

@rebloor
Copy link
Copy Markdown
Collaborator

@rebloor rebloor commented May 20, 2026

Description

Update various content to note that, with the exception of extensions using DevTools pages, browsers based on Chromium 148 support the browser namespace for the WebExtension APIs.

Motivation

To provide up-to-date information on Chrome's browser namespace support.

Related issues and pull requests

MDN content changes made in mdn/content#44149

Comment thread src/content/documentation/develop/browser-compatibility.md Outdated

Starting with Chromium 148, Chrome supports the `browser` namespace and promises (except for extensions with a DevTools page), meaning all major browsers now support the `browser` namespace. For more information, see [Transition to browser namespace](https://developer.chrome.com/docs/extensions/develop/concepts/browser-namespace).

For Chrome extensions that don't use the `browser` namespace, most of the [WebExtension APIs](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API) provide support for callback functions under the `chrome` namespace. The only APIs that aren't supported in the `chrome` namespace are those that are incompatible with Chrome or support Firefox only features. In those cases, the API documentation page states that support is provided only in the `browser` namespace.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm not aware of any APIs that are only available in the browser namespace but not in chrome. Could you drop this and (as a new task) verify that we don't make the assumption "browser namespace defined = Firefox" anywhere in mdn (content / examples)?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@Rob--W we state in the note on proxy, given that the API is incompatible with Chrome's version. Also, what about contextualIdentities? It's not documented, but it's an API not available in Chrome. (I'll check shortly.) If either or both of these hold true, perhaps we should change this to an explicit list (assuming there aren't any others).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@Rob--W we state in the note on proxy, given that the API is incompatible with Chrome's version.

That note is inaccurate.

Also, what about contextualIdentities?

Also available to both namespaces. There are common cross-browser APIs and unique browser-specific APIs.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Thanks @Rob--W updated, and I'll set up a new PR for MDN next.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Comment thread src/content/documentation/develop/manifest-v3-migration-guide.md Outdated
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