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.

Sign up for GitHub

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

Small editorial cleanup to DeclarativeWebPush #104

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Small editorial cleanup to DeclarativeWebPush #104

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
88497b1
Small editorial cleanup to DeclarativeWebPush
beidson Sep 13, 2023
21c08ca
Merge branch 'main' into main
marcoscaceres May 9, 2024
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
7 changes: 4 additions & 3 deletions DeclarativeWebPush/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ The [W3C’s Push API](https://www.w3.org/TR/push-api/) and related specificatio

Push notifications that come in to an OS platform generally contain a payload describing a user visible notification that the platform can display itself, without any app code executing.

It is also fairly standard practice for platforms to grant small pieces of an application limited CPU time to *transform* an incoming push notification. Some examples of these tasks include decrypting push data with device-local keys, updating the notification based on up-to-the-minute scores from an in-progress sporting event, or calculating a new unread count for the application badge.
It is also fairly standard practice for platforms to grant small pieces of an application limited CPU time to *transform* an incoming push notification. Some examples include decrypting push data with device-local keys, updating the notification based on up-to-the-minute scores from an in-progress sporting event, or calculatng a new unread count for the application badge.

If the app fails to complete a transformation task in its allotted time — due to coding error or other factors outside its control — then the original notification is displayed to the user by the platform. This automatic recovery model avoids disrupting the user experience, and ensures that push notifications don’t become a vector for untrusted silent background runtime.

Expand All @@ -61,7 +61,7 @@ We detail how this model works in the sections below.

## Our proposal

We believe everybody benefits from a model where a push message directly declares a user visible notification that the platform can display. We also believe the existing Web Push standards — as well as the infrastructure in use on the web — have proven reliable, and any new standards should build on them.
We believe everybody benefits from a model where a push message directly declares a user visible notification that the platform can display. We also believe the existing Web Push standards, as well as the Web Push infrastructure in use on the web, have proven reliable. Any new standards should build on them.

We are **not** proposing that Declarative Web Push replace the existing Web Push model, but rather that it be an optional model for web developers to provide better experiences for all.

Expand Down Expand Up @@ -108,7 +108,8 @@ Push messages received with that content type are considered to have a `notifica
A neat trick here is that many legacy Service Worker `push` event handlers simply transcribe an application-specific JSON description of a `Notification` into their call to `ServiceWorkerRegistration.showNotification`

By switching their JSON format over to the new standard format, their JSON payload becomes backwards compatible with other browsers that don’t have support for Declarative Web Push.
By sending all of their push messages with `Content-Type: application/notification+json`, newer browsers that support Declarative Web Push can handle the notification in an efficient, privacy-preserving manner, and older browsers that haven't updated yet will still receive the push message and fire a `push` event to the Service Worker like usual.

By sending all of their push messages with `Content-Type: application/notification+json`, newer browsers that support Declarative Web Push can handle the notification in the efficient, privacy preserving manner, and older browsers that haven't updated yet will still receive the push message and fire a `push` event to the Service Worker like usual.

## Push API - Push Subscription

Expand Down