Closed
Bug 851250
Opened 12 years ago
Closed 9 years ago
Acknowledge push notification only when app has successfully started and been delivered the notification
Categories
(Core :: DOM: Push Subscriptions, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: nsm, Unassigned)
References
Details
It is possible that the app may not get the system message because there isn't enough memory to start the application. The push service should not send an acknowledgement to the server in that case.
Reporter | ||
Comment 1•12 years ago
|
||
Another case:
App X registers for push
App X is updated, and manifest no longer declares push permission
Push notification comes in.
In this case system messages will not wake up the application. PushService should receive some sort of error from system message and unregister or similar.
Updated•12 years ago
|
Component: General → DOM: Push Notifications
Product: Boot2Gecko → Core
Version: unspecified → Trunk
Reporter | ||
Comment 2•9 years ago
|
||
This isn't urgent at all, but something to think about in the future. The delivery of events to Service Workers has only recently been specced out a bit more - https://github.com/slightlyoff/ServiceWorker/issues/649
Assignee: nsm.nikhil → nobody
Comment 3•9 years ago
|
||
End-to-end acks have been discussed for Web Push a few times, but I think they're abandoned. We currently nack worker delivery failures; this could be extended to send an end-to-end ack if there's interest.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•