Notification Triggers support

Published 2026-09-032026-09-03By Carey Gill · Editorial process

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

Browser & ecosystem support

Legend
Yes
Partial
Flag
No
Unknown

Browser / Platform	Support	Versions	Confidence	Source	Notes
Chrome (Desktop)	No	—	medium	source	¹²

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

How to use it

The proposed shape, from the explainer, passed a showTrigger option alongside a TimestampTrigger set to the desired delivery time:

async function scheduleNotification(registration, whenMs, options) {
  return registration.showNotification('Reminder', {
    ...options,
    showTrigger: new TimestampTrigger(whenMs),
  });
}

How to detect it at runtime

The documented way to check for support was testing for showTrigger on Notification.prototype. Because Chrome’s own documentation says development of the feature ended, treat that check as unreliable and always implement the fallback branch:

function scheduleWithFallback(registration, whenMs, options) {
  if ('showTrigger' in Notification.prototype) {
    return registration.showNotification('Reminder', {
      ...options,
      showTrigger: new TimestampTrigger(whenMs),
    });
  }
  // Fallback: hand the schedule to a server-driven push message instead.
  return requestServerScheduledPush(whenMs, options);
}

Practical checklist

Chrome’s own documentation states that development of this feature has ended, so do not rely on showTrigger being available — always implement and exercise the fallback branch shown above.
Per that documentation, the reason given was an unsolved need to prune stale or invalidated scheduled notifications (for example, a canceled calendar event) without relying on a tab staying open, and the write-up says the Push API and Periodic Background Sync were considered and found insufficient for that specific need.
Because the API never reached general availability, do not assume any future browser version will add it without checking current MDN or Chrome status documentation first.

Where to go next

← Back to the Compatibility explorer.