Re: [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200)

How would this impact the code of someone using `PushSubscription.options`? In case of `userVisibleOnly`, since `undefined` is falsy, I suspect we're good. This might be more of a concern for VAPID's `applicationServerKey`.

The (supposedly) common case of using this to resubscribe would not be impacted:
```javascript
self.addEventListener('pushsubscriptionchange', event => {
  event.waitUntil(
      pushManager.subscribe(event.oldSubscription.options).then(...));
});
```

What about the following addition after the first paragraph of section 8.1?
> These options are optional, and user agents MAY choose to support only a subset of them. User agents SHOULD NOT expose options it does not support.

Somewhat orthogonal, but I would very much like to see this for notifications too: exposing properties based on availability of the feature on the user's host platform.

---
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/200#issuecomment-232394949