Наши волонтёры ещё не перевели данную статью на Русский. Присоединяйтесь к нам и помогите сделать эту работу!
Вы можете также прочитать эту статью на English (US).

Use this event to listen for messages from another part of your extension. For example, you can use it:
  • in a content script, to listen for messages from a background script
  • in a background script, to listen for messages from a content script
  • in an options page or popup script, to listen for messages from a background script
  • in a background script, to listen for messages from an options page or popup script

To send a message which will be received by the onMessage listener, use runtime.sendMessage() or (to send a message to a content script) tabs.sendMessage().

Along with the message itself, the listener is passed:

  • a sender object giving details about the message sender
  • a sendResponse function which it can use to send a response back to the sender.

You can send a synchronous response to the message by calling the sendResponse function inside your listener. See an example.

To send an asynchronous response, there are two options:

  • return true from the event listener. This keeps the sendResponse function valid after the listener returns, so you can call it later. See an example.
  • return a Promise from the event listener, and resolve when you have the response (or reject it in case of an error). See an example.

Returning a Promise is now preferred as sendResponse will be removed from W3C spec. The popular webextension-polyfill library has already removed the sendResponse function from its implementation.

In Firefox versions prior to version 51, the runtime.onMessage listener will be called for messages sent from the same script (e.g. messages sent by the background script will also be received by the background script). In those versions of Firefox, if you unconditionally call runtime.sendMessage() from within a runtime.onMessage listener, you will set up an infinite loop which will max-out the CPU and lock-up Firefox. If you need to call runtime.sendMessage() from within a runtime.onMessage, you will need to check the sender.url property to verify you are not sending a message in response to a message which was sent from the same script. This bug was resolved as of Firefox 51.



Events have three functions:

Adds a listener to this event.
Stop listening to this event. The listener argument is the listener to remove.
Checks whether a listener is registered for this event. Returns true if it is listening, false otherwise.

addListener syntax



A listener function that will be called when this event occurs. The function will be passed the following arguments:

object. The message itself. This is a JSON-ifiable object.
A runtime.MessageSender object representing the sender of the message.

A function to call, at most once, to send a response to the message. The function takes a single argument, which may be any JSON-ifiable object. This argument is passed back to the message sender.

If you have more than one onMessage listener in the same document, then only one may send a response.

To send a response synchronously, call sendResponse before the listener function returns. To send a response asynchronously:

  • either keep a reference to the sendResponse argument and return true from the listener function. You will then be able to call sendResponse after the listener function has returned.
  • or return a Promise from the listener function and resolve the promise when the response is ready. This is a preferred way.

The listener function can return either a Boolean or a Promise.

Browser compatibility

Update compatibility data on GitHub
ChromeEdgeFirefoxOperaFirefox for Android
onMessageChrome Full support 26Edge Full support 14Firefox Full support 45Opera Full support 15Firefox Android Full support 48
Respond with PromiseChrome No support NoEdge No support NoFirefox Full support YesOpera No support NoFirefox Android Full support Yes


Full support  
Full support
No support  
No support


Simple example

This content script listens for click events in the web page. If the click was on a link, it messages the background page with the target URL:

// content-script.js

window.addEventListener("click", notifyExtension);

function notifyExtension(e) {
  if (e.target.tagName != "A") {
  browser.runtime.sendMessage({"url": e.target.href});

The background script listens for these messages and displays a notification using the notifications API:

// background-script.js


function notify(message) {
    "type": "basic",
    "iconUrl": browser.extension.getURL("link.png"),
    "title": "You clicked a link!",
    "message": message.url

Sending a synchronous response

This content script sends a message to the background script when the user clicks in the page. It also logs any response sent by the background script:

// content-script.js

function handleResponse(message) {
  console.log(`background script sent a response: ${message.response}`);

function handleError(error) {
  console.log(`Error: ${error}`);

function sendMessage(e) {
  var sending = browser.runtime.sendMessage({content: "message from the content script"});
  sending.then(handleResponse, handleError);  

window.addEventListener("click", sendMessage);

Here is a version of the corresponding background script, that sends a response synchronously, from inside in the listener:

// background-script.js

function handleMessage(request, sender, sendResponse) {
  console.log(`content script sent a message: ${request.content}`);
  sendResponse({response: "response from background script"});


And here is another version, that uses Promise.resolve():

// background-script.js

function handleMessage(request, sender, sendResponse) {
  console.log(`content script sent a message: ${request.content}`);
  return Promise.resolve({response: "response from background script"});


Sending an asynchronous response using sendResponse

Here is an alternative version of the background script from the previous example. It sends a response asynchronously, after the listener has returned. Note return true; in the listener: this tells the browser that you intend to use the sendResponse argument after the listener has returned.

// background-script.js

function handleMessage(request, sender, sendResponse) {  
  console.log(`content script sent a message: ${request.content}`);
  setTimeout(() => {
    sendResponse({response: "async response from background script"});
  }, 1000);  
  return true;


Sending an asynchronous response using a Promise

This content script gets the first <a> link in the page, and sends a message asking if the link's location is bookmarked. It expects to get a Boolean response: true if the location is bookmarked, false otherwise:

// content-script.js

const firstLink = document.querySelector("a");

function handleResponse(isBookmarked) {
  if (isBookmarked) {

  url: firstLink.href

Here is the background script. It uses bookmarks.search() to see if the link is bookmarked, which returns a Promise:

// background-script.js

function isBookmarked(message, sender, response) {
  return browser.bookmarks.search({
    url: message.url
  }).then(function(results) {
    return results.length > 0;


If the asynchronous handler doesn't return a promise, you can explicitly construct a promise. This rather contrived example sends a response after a 1 second delay, using Window.setTimeout():

// background-script.js

function handleMessage(request, sender, sendResponse) {
  return new Promise(resolve => {
    setTimeout(() => {
      resolve({response: "async response from background script"});
    }, 1000);


Example extensions


This API is based on Chromium's chrome.runtime API. This documentation is derived from runtime.json in the Chromium code.

Microsoft Edge compatibility data is supplied by Microsoft Corporation and is included here under the Creative Commons Attribution 3.0 United States License.

Метки документа и участники

Внесли вклад в эту страницу: mdnwebdocs-bot, irenesmith, kernp, wbamberg, iyyu, juraj, dlwe, andrewtruongmoz, lemnis, Makyen, chrisdavidmills
Обновлялась последний раз: mdnwebdocs-bot,