Browser APIs and compatibility

Start with an inventory of the extension’s API calls. For each method and event, record the required browser versions and inspect the compatibility information. MDN’s cross-browser extension guide identifies differences in API coverage, namespaces, asynchronous handling and script execution.

Review calls under browser.* and chrome.* against those target versions. Record whether the code expects a Promise or callback, including responses from message handlers. Support for a namespace alone does not settle the behavior of every method or event.

If a feature is missing, define the alternative behavior before implementation. MDN recommends checking feature availability at runtime when selecting a fallback.

For Chrome-to-Edge work, Microsoft’s porting guide starts with checking the APIs used against Edge’s supported list. Include that review even when much of the code is shared.

Manifest and permissions

Review manifest.json for each browser package. MDN’s manifest reference describes the keys for metadata, permissions and features. Keep each requested permission and website scope tied to the product action that needs it.

Background execution needs particular attention. MDN describes Chrome’s Manifest V3 extension service workers and Firefox’s background pages. Check the background configuration and behavior for the actual targets.

Microsoft’s porting checklist also calls for removing update_url, adjusting Chrome-specific naming for Edge and testing the package by sideloading it. These are concrete package checks to keep with the API inventory.

Treat each browser’s package and store listing as separate release assets. MDN describes separate submission processes for the stores; a completed local test does not establish a store review outcome.

What changes in a Chrome and Firefox manifest?

Teaching fragments for Manifest V3. The example targets Chrome 121 or later and Firefox 121 or later. These are partial manifests for illustrating the background configuration, not an Extcorp stack or completed project.

For the Chrome package:

{
  "manifest_version": 3,
  "background": {
    "service_worker": "background.js"
  }
}

For the Firefox package:

{
  "manifest_version": 3,
  "background": {
    "scripts": ["background.js"]
  }
}

MDN’s background reference documents Chrome’s service-worker environment and Firefox’s background scripts. It also describes changes at version 121 in how the browsers handle background keys intended for the other environment. Each fragment above selects only its own environment.

Run the setting-persistence scenario in the next section for both targets. Record the actual browser version and result for each package.

How to build a browser acceptance matrix

Choose the same useful product scenario for every target. For example, the scenario could be saving a setting, closing the panel and checking that the value persists after reopening it. This is an acceptance check, not a claim about a completed project.

Fill in a matrix like this:

Template for recording browser compatibility checks
Browser and versionCompatibility checksAcceptance record
Chrome: specify versionAPI calls, permissions, background behavior and package manifestScenario, expected behavior, observed result and evidence
Edge: specify versionSupported APIs, permissions, porting checklist and sideloaded packageThe same scenario, expected behavior, observed result and evidence
Firefox: specify versionAPI coverage, asynchronous handling, permissions and background configurationThe same scenario, expected behavior, observed result and evidence

Add rows for other required versions. Record the extension build and test environment with each result. When behavior differs, describe the affected action and the accepted fallback so another person can repeat the check.

Prepare the development brief

Turn the inventory and matrix into requirements:

  • State the user’s main action and what already exists.
  • List the browsers and versions that need acceptance.
  • Include API dependencies, permissions, website access and integrations.
  • Define expected behavior, fallbacks and the evidence needed for each check.
  • Separate code changes, packaging and store-submission responsibilities.

The browser extension project brief provides a copyable structure. If you are still choosing between an existing product and new work, use the buy-or-build comparison.

Extcorp reviews browser coverage, permissions, integrations and the current project state through its browser extension development services. Send the requirements and matrix to discuss the work to be included.

Discuss extension development

Extcorp is independent of Google, Microsoft and Mozilla.