Re: [w3c/push-api] Consider including `supportedContentEncodings` in the `PushSubscription` serializer (#277)

The main problem with this is that it as a static, it isn't obvious that it will be folded in to the serialized form of a instance.

It's also not strictly a property of the subscription.  Say that we deploy "rot13" tomorrow in Firefox, then we'll start to accept messages encrypted using "rot13" even if the subscription was created before "rot13" was deployed.  Worse, when we back "rot13" out in a mad rush, the subscriptions created while it was present will be forever marked as being valid for use with "rot13", even if the browser has long since removed that capability.

That highlights an inherent flaw in the definition of `supportContentEncodings`, but I think that it's manageable as it is.

-- 
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/277#issuecomment-314291381