Contact emails
antoniosart...@chromium.org

Explainer
None


Specification
https://w3c.github.io/push-api/#the-pushsubscriptionchange-event


Summary

Fire the pushsubscriptionchange event in service workers when an origin for 
which a push subscription existed in the past, but which was revoked because of 
a permission change (from granted to deny/default), is re-granted notification 
permission. The event will be fired with an empty oldSubscription and 
newSubscription.



Blink component
Blink>PushAPI


TAG review
None


TAG review status
Not applicable


Risks




Interoperability and Compatibility

None


Gecko: Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=1497429) 
Firefox seems to already implement a similar behavior, see 
https://bugzilla.mozilla.org/show_bug.cgi?id=1497429

WebKit: No signal Seems shipped, but couldn't figure out the exact details. See 
https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerGlobalScope/pushsubscriptionchange_event

Web developers: No signals Likely positive, see for example 
https://issues.chromium.org/issues/40129474

Other signals:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?

None




Debuggability

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
ChromeOS, Android, and Android WebView)?
No


Is this feature fully tested by web-platform-tests?
No


Flag name on about://flags
None


Finch feature name
PushSubscriptionChangeEventOnResubscribe


Rollout plan
Will ship enabled for all users


Requires code in //chrome?
False


Tracking bug
https://issues.chromium.org/issues/407523313


Launch bug
https://launch.corp.google.com/launch/4390563


Estimated milestones


Shipping on desktop 137

Shipping on Android 137




Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop 
issues. Please list open issues (eg links to known github issues in the project 
for the feature specification) whose resolution may introduce web 
compat/interop risk (eg, changing to naming or structure of the API in a 
non-backward-compatible way).
None


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5147683423256576?gate=5097638464323584


Links to previous Intent discussions
Intent to Prototype: 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOzWxF6xvYb-0qkPaZbhNFuS86__DEg8curFPGRtuDak8x%3D31g%40mail.gmail.com



This intent message was generated by Chrome Platform Status.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6800bf60.170a0220.3d0732.00f6.GAE%40google.com.

Reply via email to