The Web Push API (https://www.w3.org/TR/push-api/) defines a PushSubscriptionOptions object which allows a subscription to specify whether it is userVisibleOnly. If a subscription is userVisibleOnly, then the service worker will always display some user visible effect when allowed to run as a result of a push message. Currently, Chrome only supports subscriptions with userVisibleOnly set to true.
Chrome has already shifted the existing default notification grace count to using a budget service based on the user's engagement with the site. That system should be expanded to allow limited processing without visible effects.
The system should also provide a developer query-able API to get current and future budget information, so that developers can provide a more app-like experience.
The system should provide a developer query-able API to get current and future budget information, so that developers can provide a more app-like experience. This budget can be used by user agent developers to control access to resource intensive background operations.
As a first implementation, we should allow push messages to trigger background processing without always showing a notification.
The Web Push API (https://www.w3.org/TR/push-api/) defines a PushSubscriptionOptions object which allows a subscription to specify whether it is userVisibleOnly. If a subscription is userVisibleOnly, then the service worker will always display some user visible effect when allowed to run as a result of a push message. Currently, Chrome only supports subscriptions with userVisibleOnly set to true.
Chrome has already shifted the existing default notification grace count to using a budget service based on the user's engagement with the site. That system should be expanded to allow limited processing without visible effects.
Comment 1 by bugdroid1@chromium.org
, Jun 8 2016