Skip to content

Notification Triggers browser support

Published

Notification Triggers was a proposed showTrigger option for ServiceWorkerRegistration.showNotification() that would schedule a notification for a future time, chosen with a TimestampTrigger, without the page or service worker running when it fired.

The table has a single Chrome row sourced from Chrome Platform Status, because no BCD or caniuse dataset tracks the feature: after an explainer and two origin trials (Chrome 80 to 83 and 86 to 88) its launch milestone is “Not started”, and Chrome’s documentation confirms development has ended. The row makes no claim about any other engine.

  • Legend
  • Yes
  • Partial
  • Flag
  • No
  • Unknown
Browser / PlatformSupportVersionsConfidenceSourceNotes
Chrome (Desktop)No—mediumsource12
  1. Never shipped in Chrome: Chrome Platform Status lists the feature's Launch milestone as "Not started" after completing an explainer and two origin trials (Chrome 80-83 and 86-88); Chrome's own documentation confirms development has ended.
  2. This row is sourced from Chrome's own status page and proves Chrome's status only; it makes no claim about any other browser engine.

Source data: /compatibility/notification-triggers.json · Global usage: 0 % (StatCounter 2026-05)

Source: spec · MDN · Last verified 2026-09-03 · Confidence: medium (computed from sources)

Chrome’s write-up gives the reason as an unsolved need to prune stale or invalidated scheduled notifications (for example a cancelled calendar event) without relying on an open tab, and says the Push API and Periodic Background Sync were considered and found insufficient for that specific need. Scheduling through a server-sent push message remains the documented alternative.