ServiceWorkerGlobalScope

ServiceWorkerGlobalScope.clients 只读

Contains the Clients object associated with the service worker.

ServiceWorkerGlobalScope.registration 只读

Contains the ServiceWorkerRegistration object that represents the service worker's registration.

ServiceWorkerGlobalScope.caches 只读

Contains the CacheStorage object associated with the service worker.

activate

Occurs when a ServiceWorkerRegistration acquires a new ServiceWorkerRegistration.active worker.

contentdelete 实验性

Occurs when an item is removed from the Content Index.

fetch

Occurs when a fetch() is called.

install

Occurs when a ServiceWorkerRegistration acquires a new ServiceWorkerRegistration.installing worker.

message

Occurs when incoming messages are received. Controlled pages can use the MessagePort.postMessage() method to send messages to service workers. The service worker can optionally send a response back via the MessagePort exposed in event.data.port, corresponding to the controlled page.

notificationclick

Occurs when a user clicks on a displayed notification.

notificationclose

Occurs when a user closes a displayed notification.

sync

Triggered when a call to SyncManager.register is made from a service worker client page. The attempt to sync is made either immediately if the network is available or as soon as the network becomes available.

periodicsync 实验性

Occurs at periodic intervals, which were specified when registering a PeriodicSyncManager.

push

Occurs when a server push notification is received.

pushsubscriptionchange

Occurs when a push subscription has been invalidated, or is about to be invalidated (e.g. when a push service sets an expiration time).

ServiceWorkerGlobalScope.skipWaiting()

Allows the current service worker registration to progress from waiting to active state while service worker clients are using it.

ServiceWorkerGlobalScope implements WorkerGlobalScope — which implements GlobalFetch. Therefore it also has the following property available to it:

GlobalFetch.fetch()

Starts the process of fetching a resource. This returns a promise that resolves to the Response object representing the response to your request. This algorithm is the entry point for the fetch handling handed to the service worker context.

This code snippet is from the service worker prefetch sample (see prefetch example live.) The ServiceWorkerGlobalScope.onfetch event handler listens for the fetch event. When fired, the code returns a promise that resolves to the first matching request in the Cache object. If no match is found, the code fetches a response from the network.

The code also handles exceptions thrown from the fetch() operation. Note that an HTTP error response (e.g., 404) will not trigger an exception. It will return a normal response object that has the appropriate error code set.

self.addEventListener("fetch", function (event) {
  console.log("Handling fetch event for", event.request.url);

  event.respondWith(
    caches.match(event.request).then(function (response) {
      if (response) {
        console.log("Found response in cache:", response);

        return response;
      }
      console.log("No response found in cache. About to fetch from network...");

      return fetch(event.request).then(
        function (response) {
          console.log("Response from network is:", response);

          return response;
        },
        function (error) {
          console.error("Fetching failed:", error);

          throw error;
        },
      );
    }),
  );
});

• 使用 Service Worker
• Service worker 基本代码示例
• 是否支持 ServiceWorker
• Promise
• 使用 web worker