Set a reasonable PushSubscription.expirationTime
Categories
(Core :: DOM: Push Subscriptions, enhancement, P3)
Tracking
()
People
(Reporter: marcosc, Unassigned)
Details
(Keywords: dev-doc-needed)
Reporter | ||
Updated•7 years ago
|
Updated•7 years ago
|
Comment 1•6 years ago
|
||
I think this should be blocked on implementing the latest pushsubscriptionchange
spec that passes both oldSubscription
and newSubscription
to the event handler, as well as blocked on the one-off background sync API (https://bugzilla.mozilla.org/show_bug.cgi?id=1217544), otherwise it will be hard for web developers to reliably handle subscription refreshes.
Comment 2•6 years ago
|
||
I think that makes sense—here's the bug for implementing the latest pushsubscriptionchange
event.
Comment 3•6 years ago
|
||
First of all the standard should be fixed, as I have reported here:
https://github.com/WICG/BackgroundSync/issues/147
Currently the Background Sync can only be used when a window is open, but the pushsubscriptionchange can be triggered at any time... i.e. currently you cannot use Background Sync inside pushsubscriptionchange.
Updated•3 years ago
|
Description
•