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

Presumably, if the UA doesn't support member X, then it can omit X from `PushSubscription.options`.  Given that the most obvious use for that is to pass it back to the UA, then not having X will be functionally equivalent (since the UA would ignore X even if it is present).

Even if it did retain X, there would be no harm other than muddying the situation: applications wouldn't be able to work out what was supported vs. not.

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

Yes, feature detection is a basic right :)

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

Received on Thursday, 14 July 2016 00:57:05 UTC