Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PushManager.supportedContentEncodings updates #36962

Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,23 @@ browser-compat: api.PushManager.supportedContentEncodings_static

{{APIRef("Push API")}}{{SecureContext_Header}}{{AvailableInWorkers}}

The **`supportedContentEncodings`** read-only static property of the
{{domxref("PushManager")}} interface returns an array of supported content codings that
can be used to encrypt the payload of a push message.
The **`supportedContentEncodings`** read-only static property of the {{domxref("PushManager")}} interface returns an array of supported content codings that can be used to encrypt the payload of a push message.

<!-- The content coding is indicated using the {{httpheader("Content-Encoding")}} HTTP header field when requesting the sending of a push message from the push service. -->
hamishwillee marked this conversation as resolved.
Show resolved Hide resolved

User agents must support the `aes128gcm` content coding defined in {{rfc("8291")}}, and may also support content codings defined from previous versions of the specification.

Note that the returned array is frozen, and may not be modified by the recipient.

## Value

An array of strings.

## Exceptions

- `TypeError`
- This is thrown when attempting to set a value in the returned array.

## Specifications

{{Specifications}}
Expand Down