New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 753163 link

Starred by 7 users
Status: Assigned
Owner:
hhli@chromium.org
Cc:
█ tjsavage@chromium.org
█ beverloo@chromium.org
addyo@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 646721


Sign in to add a comment

Add the ability to trigger a push subscription change event

Project Member Reported by mattgaunt@chromium.org, Aug 7 2017 
As more browsers implement web push, some are requiring developers to implement pushsubscriptionchange and it would help if devtools added the ability for developers to trigger the event to test their logic.

Would be a nice to have if you could offer common edge cases for developers to catch as well, such as triggering the event with a new PushSubscription and passing the old PushSubscription in with the event.

https://w3c.github.io/push-api/#x11.3-the-pushsubscriptionchange-event
Pushsubscriptionchange Event.png
26.2 KB View Download

Comment 1 by eostroukhov@chromium.org, Oct 3 2017

Blockedon: 646721

Comment 2 by pfeldman@chromium.org, Oct 4 2017

Owner: eostroukhov@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by collimar...@gmail.com, Sep 3 

+1 It would be useful to trigger a refresh (https://www.w3.org/TR/push-api/#subscription-refreshes) from dev tools for testing pushsubscriptionchange. 

Currently there is no way to test it! Indeed if you block and then allow the notifications you will never get the "refresh" event - the events triggered in this way don't have oldSubscription and newSubscription...

Comment 4 by dgozman@chromium.org, Oct 12

Owner: hhli@chromium.org
►

Sign in to add a comment