Supporting server authentication and subscription restrictions from the following IETF draft, that will allow developers to provide a public key when subscribing for push upon which Chrome will return a Web Push protocol-compatible endpoint. https://tools.ietf.org/html/draft-thomson-webpush-vapid-02 This will enable us to move away from our current GCM implementation requirements.
Documentation
Specification
Status in Chromium
Enabled by default (tracking bug) in:
- Chrome for desktop release 52
- Chrome for Android release 52
Consensus & Standardization
After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.
- Shipped/Shipping
- No signal
- No signal
- Strongly positive
Owner
Search tags
push, notifications,Last updated on 2021-01-04