← back to v138 · pushsubscriptionchange-event-upon-resubscription
conformance · v138
v138 · pushsubscriptionchange-event-upon-resubscription — conformance probe
5 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
service-worker-supported |
ServiceWorker is exposed — required to observe pushsubscriptionchange events. spec ↗ | exists | … | |
push-manager-defined |
PushManager is defined — the surface that emits pushsubscriptionchange. spec ↗ | exists | … | |
pushsubscriptionchange-event-interface |
PushSubscriptionChangeEvent is exposed in window scope (so its shape — oldSubscription, newSubscription — is observable). spec ↗ | script | … | |
permissions-query-notifications |
permissions.query({name:'notifications'}) returns a promise — the surface a page uses to read the permission state whose change re-fires pushsubscriptionchange. spec ↗ | script | … | |
notification-permission-readable |
Notification.permission is readable — the state observable by the page that triggers the resubscription event. spec ↗ | script | … |