No tag review, as this is a small addition to an existing spec.
The Notification.actions attribute will not be shipped yet, rather like we didn't ship Notification.vibrate, since Chrome does not yet support FrozenArray. It's only a convenience attribute though, and the parts being shipped form a coherent whole without it.
We haven't yet spec'ed or implemented icons for action buttons, but those will likely be added later.
These allow users to quickly handle the most common tasks for a particular notification, without having to open the originating website.
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)?
All except WebView, since notifications aren't yet supported there.
Sample code: https://notifications.spec.whatwg.org/#using-actions
Demo: https://tests.peter.sh/notification-generator/ (currently requires --enable-blink-features=NotificationExperimental before Actions can be used).
Breakpoints can be set in the notificationclick event as usual.
OWP launch tracking bug
Entry on the feature dashboardhttps://www.chromestatus.com/features/5906566364528640
This is an important feature frequently used by native apps, and a frequently heard request from both developers and partners.
While the omission of Notification.actions is unfortunate, it won't limit developers in providing functionality because of the NotificationEvent.action attribute.
However, we need to be cautious to not end up with too many partially shipped features because of not supporting FrozenArray<>. There's a bug tracking adding support for it.
LGTM1Has there been a tag review for notifications in general yet? I agree we don't want to send each little addition to the TAG, they should probably have a look at the spec all together at some point.