startMessages()
方法在
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.
注意
: The messages start being sent automatically when setting the handler directly using
ServiceWorkerContainer.onmessage
. In this you don't need
startMessages()
.
serviceWorkerContainer.startMessages();
None.
undefined
.
if('serviceWorker' in navigator) {
navigator.serviceWorker
.register('/sw.js')
.then(function() { console.log('Service Worker Registered'); });
}
// ...
navigator.serviceWorker.addEventListener('message', (e) => {
// ...
});
navigator.serviceWorker.startMessages();
| 规范 | 状态 | 注释 |
|---|---|---|
|
服务工作者
The definition of 'ServiceWorkerContainer: startMessages()' in that specification. |
工作草案 | 初始定义。 |
| 桌面 | 移动 | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
startMessages
|
Chrome 74 | Edge ≤79 | Firefox 64 | IE 不支持 No | Opera 62 | Safari Yes | WebView Android 74 | Chrome Android 74 | Firefox Android 64 | Opera Android 50 | Safari iOS Yes | Samsung Internet Android 11.0 |
完整支持
不支持
ServiceWorkerContainer