Re: [w3c/push-api] pushsubscriptionchange event doesn't have oldSubscription in it. (#325)

There are two things going on here, so maybe we could do a little to extract them:

1. if a subscription is terminated, does pushsubscriptionchange fire?
2. if a subscription changes, what information needs to be included in the event?

The original question was about the information in the event (2); but that question is about termination (1).  I believe that the purpose of the event was to signal termination (with `event.newSubscription == null`), but if that has not been implemented.  Maybe we need to reconsider that idea in the face of browsers not choosing to follow the spec.  No point in a fictional specification.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/325#issuecomment-948265195