Re: [push-api] PushSubscription should have an attribute for ExpirationTime (#86)

It seems valid, but how is it different from `pushsubscriptionchange`? Is the difference important enough to expand the API?

Note also that `pushsubscriptionchange` is more general, it can handle other reasons for refreshing the subscription e.g. if we later added encryption (issue #55), it can be fired because the encryption key was rotated.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/86#issuecomment-70531903