Intent to Ship: Notification `actions` and `vibrate` attributes

[Peter Beverloo]

Contact emails

johnme@chromium,org, sh919...@samsung.com (did the work)

pe...@chromium.org (flag flipper)

Spec

https://notifications.spec.whatwg.org/

Summary

Support for both notification action buttons and developer-provided vibrations have shipped already, but we weren't able to expose the matching read-only properties on instances of the Notification object because of their intended semantics.

Now that the bindings team has kindly added support for FrozenArray and [SameObject], we can get these out of the door too :-).

https://groups.google.com/a/chromium.org/d/topic/blink-dev/6tlbJW0NjEA/discussion

https://groups.google.com/a/chromium.org/d/topic/blink-dev/hLhTAOXfRTo/discussion

CL: https://codereview.chromium.org/1974033003/

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

All platforms where notifications are supported.

Debuggability

Improved, because developers (and DevTools) can now read back the action and vibrate properties passed to a shown notification.

It also allows developers to feature-check for presence of action buttons and vibration patterns:

const actionButtonsSupported = Notification.prototype.hasOwnProperty('actions');

const vibrateSupported = Notification.prototype.hasOwnProperty('vibrate');

Interoperability and Compatibility Risk

No risks.

OWP launch tracking bug

https://crbug.com/547716 (`actions`)

https://crbug.com/442132 (`vibrate`)

Entry on the feature dashboard

https://www.chromestatus.com/feature/5906566364528640 (`actions`)

https://www.chromestatus.com/feature/5727996321202176 (`vibrate`)

[Chris Harrelson]

LGTM1

--
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.

[Rick Byers]

LGTM2

[Dimitri Glazkov]

LGTM3.