↑ arvau

MDN / ServiceWorkerContainer: messageerror event

The messageerror event is fired to the [` {{APIRef(“Service Workers API”)}}{{SecureContext_Header}}{{AvailableInWorkers}}

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

This event is not cancelable and does not bubble.

Syntax

Use the event name in methods like addEventListener(), or set an event handler property.

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A [` {{APIRef(“Service Workers API”)}}{{SecureContext_Header}}{{AvailableInWorkers}}

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

Examples

In this example the service worker get the client’s ID from a fetch event and then sends it a message using [` {{APIRef(“Service Workers API”)}}{{SecureContext_Header}}{{AvailableInWorkers}}

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

// service-worker.js
async function messageClient(clientId) {
  const client = await self.clients.get(clientId);
  client.postMessage("Hi client!");
}

self.addEventListener("fetch", (event) => {
  messageClient(event.clientId);
  event.respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main.js
navigator.serviceWorker.addEventListener("messageerror", (event) => {
  console.error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main.js
navigator.serviceWorker.onmessageerror = (event) => {
  console.error("Receive message from service worker failed!");
};

Specifications

Browser compatibility

See also

  • message

  • [` {{APIRef(“Service Workers API”)}}{{SecureContext_Header}}{{AvailableInWorkers}}

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

The messageerror event is fired to the {{domxref(“ServiceWorkerContainer”)}} when an incoming message sent to the associated worker can’t be deserialized/

This event is not cancelable and does not bubble/

Syntax

Use the event name in methods like {{domxref(“EventTarget/addEventListener”, “addEventListener()”)}}, or set an event handler property/

addEventListener("messageerror", (event) => { })

onmessageerror = (event) => { }

Event type

A {{domxref(“MessageEvent”)}}/ Inherits from {{domxref(“Event”)}}/

{{InheritanceDiagram(“MessageEvent”)}}

Examples

In this example the service worker get the client’s ID from a {{domxref(“ServiceWorkerGlobalScope/fetch_event”, “fetch”)}} event and then sends it a message using {{domxref(“Client/postMessage”)}}:

// service-worker/js
async function messageClient(clientId) {
  const client = await self/clients/get(clientId);
  client/postMessage("Hi client!");
}

self/addEventListener("fetch", (event) => {
  messageClient(event/clientId);
  event/respondWith(() => {
    // …
  });
});

The service worker can listen for the message deserialization error by listening to the messageerror event:

// main/js
navigator/serviceWorker/addEventListener("messageerror", (event) => {
  console/error("Receive message from service worker failed!");
});

Alternatively, the script can listen for the message deserialization error using onmessageerror:

// main/js
navigator/serviceWorker/onmessageerror = (event) => {
  console/error("Receive message from service worker failed!");
};

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also