大网数据广告活动
Web 标准与前端开发

ServiceWorkerGlobalScope

· 52CE 我爱测

ServiceWorker API 的`ServiceWorkerGlobalScope` 接口,代表一个 service worker 的全局执行上下文。

Service Workers API

ServiceWorker API 的ServiceWorkerGlobalScope 接口,代表一个 service worker 的全局执行上下文。

开发者应该知道,ServiceWorker 的状态在结束/重启的循环中不是一直保持不变的,所以每个事件处理器应该设定一个默认的全局状态。

一旦成功地注册了 service worker,为了节省内存和处理器,它将在他的状态达到了空闲的时候被终止。一个在激活状态的 service worker 为了响应事件是可以自动重启的,就像这两个方法, ServiceWorkerGlobalScope.onfetch 或者ServiceWorkerGlobalScope.onmessage.

此外,在 service worker 中,同步请求是被禁止的 - 只有异步请求,如方法GlobalFetch.fetch 才被允许。

该接口继承自 WorkerGlobalScope 接口,以及其父类 EventTarget, 因此继承属性来自 WindowTimers, WindowBase64.

属性

  • 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.

事件

  • ServiceWorkerGlobalScope/activate_event
    • : Occurs when a ServiceWorkerRegistration acquires a new ServiceWorkerRegistration.active worker.
  • ServiceWorkerGlobalScope/contentdelete_event
    • : Occurs when an item is removed from the ContentIndex.
  • ServiceWorkerGlobalScope/fetch_event
    • : Occurs when a fetch() is called.
  • ServiceWorkerGlobalScope/install_event
    • : Occurs when a ServiceWorkerRegistration acquires a new ServiceWorkerRegistration.installing worker.
  • ServiceWorkerGlobalScope/message_event
    • : 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.
  • ServiceWorkerGlobalScope/notificationclick_event
    • : Occurs when a user clicks on a displayed notification.
  • ServiceWorkerGlobalScope/notificationclose_event
    • : Occurs when a user closes a displayed notification.
  • ServiceWorkerGlobalScope/sync_event
    • : 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.
  • ServiceWorkerGlobalScope/periodicsync_event
    • : Occurs at periodic intervals, which were specified when registering a PeriodicSyncManager.
  • ServiceWorkerGlobalScope/push_event
    • : Occurs when a server push notification is received.
  • ServiceWorkerGlobalScope/pushsubscriptionchange_event
    • : 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 GlobalFetch.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;
        },
      );
    }),
  );
});

规范

浏览器兼容性

参见

来源:MDN Web Docs / Mozilla 贡献者 · 作者与贡献记录 · CC BY-SA 2.5。离线整理了版式、链接和媒体显示。

资料来源与适用范围

资料来源
MDN Web Docs / Mozilla 贡献者
适用范围
请按文中版本与环境说明核对
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 2.5

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。