The startMessages() method of the ServiceWorkerContainer interface explicitly starts the flow of messages being dispatched from a service worker to pages under its control (e.g. sent via Client.postMessage()). This can be used to react to sent messages earlier, even before that page's content has finished loading.
By default, all messages sent from a page's controlling service worker to the page (using Client.postMessage()) are queued while the page is loading, and get dispatched once the page's HTML document has been loaded and parsed (i.e. after the DOMContentLoaded event fires). It's possible to start dispatching these messages earlier by calling ServiceWorkerContainer.startMessages(), for example if you've invoked a message handler using EventTarget.addEventListener() before the page has finished loading, but want to start processing the messages right away.
Note: The messages start being sent automatically when setting the handler directly using onmessage. In this you don't need startMessages().
js
startMessages()
None.
undefined.
js
if ("serviceWorker" in navigator) { navigator.serviceWorker.register("/sw.js").then(() => { console.log("Service Worker Registered"); }); } // … navigator.serviceWorker.addEventListener("message", (e) => { // … }); navigator.serviceWorker.startMessages();
| Specification |
|---|
| Service Workers # navigator-service-worker-startMessages |
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | WebView Android | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | |
startMessages |
74 | 79 | 64 | No | 62 | 11.1 | 74 | 74 | 64 | 50 | 11.3 | 11.0 |
© 2005–2023 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerContainer/startMessages