Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228)

@beverloo 

> Would it work for you if I phrase the permission revocation scenario with SHOULD as opposed to MUST? I can see what this may be hard to support architecturally.

Yes, that would certain help from implementation perspective so the UA can have flexibility in handling corner cases.

> Since the user agent at least needs to replace the old subscription with the new one, we know there to be an association so presumably it could just read the data of the old subscription prior to removing it?

Good point.  It is certainly doable that way.  Meanwhile, would it be useful to allow the app to distinguish between two cases (a) when the old subscription is still valid, and (b) when the old subscription is invalid already?

-- 
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/228#issuecomment-263463578