The ability to create persistent notifications through ServiceWorkerRegistration.showNotification(). These notifications will be able to outlive the tab they were created by. When they get clicked on by the user, the associated Service Worker will be started (if needed) and the “notificationclick” event will be invoked. The developer can then focus existing windows, or create new ones.
On Android, we do not require the browser to be running at all for this feature to work. Desktop Chrome does have to run in order for the notifications to be displayed or to be interacted with.
Link to “Intent to Implement” blink-dev discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Windows, Mac, Linux, Chrome OS: Yes.
Android: Yes, on Android Jelly Bean and later due to the the notification UX we’d like to offer, which is unavailable on Android ICS.
Android WebView: No, because it’s not yet obvious how to support this in the WebView API. Tracked in https://crbug.com/434712
https://johnme-gcm.appspot.com/chat/ -- also uses the Push API.
Blink is the first browser engine to support the Service Worker-based Web Notifications API. Much of the discussion, however, has been led by Mozilla’s Anne van Kesteren (the editor) and Jonas Sicking.
We do not yet support the Notification.get() accessor for getting persistent notifications, nor many of the other new properties from the specification.
Addition of other new features is tracked in https://crbug.com/442145 and will be covered in future Intent to Implement and Ships.
OWP launch tracking bug?
Link to entry on the feature dashboard
Gonna sound like a broken record here, but this is *amazing*. If I could LGTM it, I would early and often and encourage OWNERS to.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.