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

@linacambridge  Thanks for the heads up.

So to sum up, I will ask a couple of questions.

1)  I can't rely on having `old` and `new` subscriptions in the `event` object of the `pushsubscriptionchange`.  Right? 

2) `pushsubscriptionchange` will still get called if mozilla decided to refresh the token. right?

3) If the above (2) is correct, should I have the code to auto subscribe a user again and send the subscription to the server?

4)  how do I get the old subscription in there so that I can send `old` one with the `new` one to the server so that I can gracefully replace old one with a new one?

5)  Is it even worth using this event at all ?

Thanks.

-- 
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-624785258