Contact emails
kno...@chromium.org, pe...@chromium.org
Spec
Explainer: https://github.com/rknoll/notification-triggers
Summary
Showing notifications at a specific time requires web applications to use the Push API. This is not ideal as it requires an active network connection and needs to wake up the browser to fetch additional data like image resources.
With this API we allow developers to prepare notifications in advance to be shown at a specific time in the future. At that time no additional network request is required anymore and no service worker code needs to run in order to show the notification.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/d/topic/blink-dev/sFb2H2pwEug/discussion
Goals for experimentation
We’d like to get developer feedback on this new API to see which use cases we haven’t thought about. We’ve designed this API to be extendable for other types of triggers (e.g. location based) if there is sufficient interest for this.
Experimental timeline
M78 - M81
Any risks when the experiment finishes?
No.
Ongoing technical constraints
None
Debuggability
Chrome DevTools already provides a UI to show events related to notifications such as scheduled, displayed and closed. Developers can also get a list of all notifications, including scheduled ones, via a JavaScript API.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Yes, except WebView as the Notification API is not supported yet (tracking bug).
Link to entry on the feature dashboard
Contact emails
kno...@chromium.org, pe...@chromium.org
Spec
Explainer: https://github.com/rknoll/notification-triggers
Summary
Showing notifications at a specific time requires web applications to use the Push API. This is not ideal as it requires an active network connection and needs to wake up the browser to fetch additional data like image resources.
With this API we allow developers to prepare notifications in advance to be shown at a specific time in the future. At that time no additional network request is required anymore and no service worker code needs to run in order to show the notification.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/d/topic/blink-dev/sFb2H2pwEug/discussion
Goals for experimentation
We’d like to get developer feedback on this new API to see which use cases we haven’t thought about. We’ve designed this API to be extendable for other types of triggers (e.g. location based) if there is sufficient interest for this.
Experimental timeline
M78 - M81
Any risks when the experiment finishes?
No.
Ongoing technical constraints
None
Debuggability
Chrome DevTools already provides a UI to show events related to notifications such as scheduled, displayed and closed. Developers can also get a list of all notifications, including scheduled ones, via a JavaScript API.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Yes, except WebView as the Notification API is not supported yet (tracking bug).
Link to entry on the feature dashboard
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKBTsuScKr2gsKF%2B9f7ca9SA1F68QdeNo6ARoFeLkXj67zFjkw%40mail.gmail.com.
Are you planning to also gather user feedback (either directly or through metrics) to make sure this is not degrading their experience?Have you considered the abuse potential for this and ways to mitigate it?(the latter question is not necessarily something that requires concrete answers before starting an OT, but it's definitely good to start asking those questions at this point)
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/42961f5b-cd1e-413f-ae1f-b09f2fa0f208%40chromium.org.
Experimental timeline
M80 - M83
Thanks!
- Richard