Contact emails
Spec
Summary
When a developer subscribes to receive push messages, the interface currently exposes “endpoint” and “subscriptionId” as two separate properties.
We would like to merge the two, and only expose “endpoint” going forward. It will be a full URL containing both the endpoint and the subscription Id. This provides better forward compatibility, as the distinction will become much less relevant when the IETF
server-to-server protocol has been standardized and implementations begin rolling it out.
In Chrome 44 we’d like PushSubscription.endpoint to contain *both* the endpoint and subscriptionId, with a deprecation warning when the developer accesses the subscriptionId independently. In Chrome 45, we’ll remove PushSubscription.subscriptionId entirely.
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes - minus Android WebView because we don’t support the Push API there.
Compatibility Risk
Medium. We are the only ones who ship the Push API, and this is a specified iteration on our implementation. Mozilla has been driving the merge of these two properties.
OWP launch tracking bug?
Link to entry on the feature dashboard
None.