1 of 6

Push API

Peter Beverloo�Google, Inc.

2 of 6

Web Push Notifications

  • W3C
    • Push API�
  • IETF
    • RFC 8030: Generic Event Delivery Using HTTP Push
    • RFC 8188: Encrypted Content-Encoding for HTTP
    • RFC 8291: Message Encryption for Web Push
    • RFC 8292: Voluntary Application Server Identification (VAPID) for Web Push�
  • WHATWG
    • Notifications API

3 of 6

Implementation status

  • Supported by Google Chrome, Microsoft Edge and Mozilla Firefox.�
    • Web Push Protocol supported by their associated push services.�
  • Significant developer adoption, together with an ecosystem of push aggregators to further expedite adoption.�
  • Advanced notification features (buttons, inline replies) need further adoption.

4 of 6

The path to Recommendation

  • Two minor additions being considered:�
    • Atomic resubscriptions (refreshSubscription())�
    • Indication on whether a notification is required on PushEvent�
  • A series of editorial issues.�
  • Please submit feedback in the next few weeks!

5 of 6

Open questions

  • Highly dependent on server behaviour and external input, making comprehensive WPT coverage challenging. wpt#5630�
  • Notification permission spam�
    • Primarily in scope for the Notification API and the permissions efforts, but something that will certainly affect developers using Web Push.

6 of 6

https://github.com/w3c/push-api