mdn / mdn/browser-compat-data

webextensions.api.runtime.onMessage - Respond with Promise is supported since Chromium 148

Open Beginner friendly
#30,194 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data:webext p3
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

Respond with Promise is supported since Chromium 148

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Browser)

What did you expect to see?

Respond with Promise should show supported since Chromium 148.

Did you test this? If so, how?

Tested in Chrome 150 that console.log(browser) in an extension service worker shows a value.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

https://developer.chrome.com/docs/extensions/develop/concepts/browser-namespace

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/onMessage

MDN metadata
MDN page report details
  • Query: webextensions.api.runtime.onMessage
  • Report started: 2026-08-07T12:24:20.145Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the MDN runtime.onMessage page and locate the repository entry for webextensions.api.runtime.onMessage. Compare the Chromium support claim with the linked Chrome browser-namespace documentation, update the compatibility data to show Promise responses from Chromium 148, and verify the resulting data passes the repository checks.

Written by the indexing model from the issue text.

Assessment

Domain
web-dev
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.