Chrome currently supports encrypted push message payloads encrypted with the `aesgcm` content encoding (draft 03). A series of substantial changes were made to the encryption drafts, yielding a new content coding: `aes128gcm` (draft 08). We'll continue to accept `aesgcm` for received push messages as well.

Specification

Working draft or equivalent

Status in Chromium

Blink>PushAPI


Enabled by default (tracking bug) in:

  • Chrome for desktop release 60
  • Chrome for Android release 60

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Positive
  • No signal
  • No signal
  • No signals

Owner

Search tags

push, api, notifications,

Last updated on 2020-11-09