Add support for inline replies

notifications.bs

@@ -108,19 +108,42 @@ the <a>notification</a>, but then it should have less visual priority than the
 is not otherwise accessible to the end user, especially since notification platforms that do not
 support these features might ignore them.
 
-<p>A <a>notification</a> has an associated list of
-zero or more <dfn for=notification lt=action id=actions>actions</dfn>. Each
-<a for=notification>action</a> has an associated
-<dfn for=action id=action-title>title</dfn> and <dfn for=action id=action-name>name</dfn> and
-<em>can</em> have an associated <dfn for=action>icon URL</dfn> and
-<dfn for=action>icon resource</dfn>. Users may activate actions, as alternatives to
-activating the notification itself. The user agent must determine the
-<dfn>maximum number of actions</dfn> supported, within the constraints of the
-notification platform.
+<p>A <a>notification</a> has <dfn for=notification lt=action id=actions>actions</dfn>, 
+a <a for=/>list</a> of <a>notification actions</a>, initially empty.
+
+<p>A <dfn id=notification-action>notification action</dfn> defines a way the user can interact with
+a notification, as an alternative to activing the notification itself.
+
+<div dfn-for="notification action">
+  <p>A <a>notification action</a> has a <dfn id=notification-action-type>type</dfn>, that is
+  "<code>button</code>" or "<code>text</code>".
+
+  <p class=note>Actions of type "<code>button</code>" can only be activated, whereas actions of type
+  "<code>text</code>" allow the user to input text during activation.
+
+  <p>A <a>notification action</a> has a <dfn id=notification-action-title>title</dfn> (a DOMString).
+
+  <p>A <a>notification action</a> has a <dfn id=notification-action-name>name</dfn> (a DOMString).
+
+  <p>A <a>notification action</a> has an <dfn id=notification-action-icon-url>icon URL</dfn> (null
+  or a <a>URL</a>). Unless stated otherwise, it is null.
+
+  <p>A <a>notification action</a> has an <dfn id=notification-action-icon-resource>icon resource</dfn>
+  (null or an image). Unless stated otherwise, it is null.
+
+  <p>A <a>notification action</a> has a <dfn id=notification-action-placeholder>placeholder</dfn>
+  (a DOMString). Unless stated otherwise, it is an empty string.
+</div>
+
+<p>The user agent must determine the <dfn>maximum number of actions</dfn> supported, within the
+constraints of the notification platform.
 
 <p class=note>Since display of actions is platform-dependent, developers are
 encouraged to make sure that any action a user can invoke from a notification is
-also available within the web application.
+also available within the web application. The ability to reply inline to
+notifications during activation is also platform-dependent, so developers are encouraged to
+handle the case where a text action was activated but the reply was null (e.g.
+by focusing a chat window).
 
 <p class="note no-backref">Some platforms might modify an <a for=action>icon resource</a> to better
 match the platform's visual style before displaying it to the user, for example by rounding the
@@ -227,14 +250,22 @@ these steps:
   <li><p>If <var>options</var>'s <code>requireInteraction</code> is true, set
   <var>notification</var>'s <a for=notification>require interaction preference flag</a>.
 
-  <li><p>Set <var>notification</var>'s list of <a>actions</a> to an empty list,
-  then for each <var>entry</var> in <var>options</var>'s <code>actions</code>,
-  up to the <a>maximum number of actions</a> supported (skip any excess
-  entries), perform the following steps:
+  <li>For each <var>entry</var> in <var>options</var>'s <code>actions</code>:
 
   <ol>
+    <li>If the user agent does not support additional actions, break.
+
     <li><p>Let <var>action</var> be a new <a lt="actions">action</a>.
 
+    <li><p>Set <var>action</var>'s <a for=action>type</a> to the <var>entry</var>'s
+    <code>type</code> property.
+
+    <li>If the user agent does not support additional actions of this
+    <a for="notification action">type</a>, continue.
+
+    <p class=note>For instance, some operating systems don't support buttons if a text action has
+    been provided, or vice-versa.
+
     <li><p>Set <var>action</var>'s <a for=action>name</a> to the <var>entry</var>'s
     <code>action</code>.
 
@@ -244,7 +275,11 @@ these steps:
     <li><p>If <var>entry</var>'s <code>icon</code> is present,
     <a lt="url parser">parse</a> it using <var>baseURL</var>, and if that does
     not return failure, set <var>action</var>'s <a for=action>icon URL</a> to the
-    return value. (Otherwise <a for=action>icon URL</a> is not set.)
+    return value.
+
+    <li><p>If <var>entry</var>'s <code>placeholder</code> is present, set
+    action's <a for=action>placeholder</a> to the <var>entry</var>'s
+    <code>placeholder</code>.
 
     <li><p>Append <var>action</var> to <var>notification</var>'s list of
     <a>actions</a>.
@@ -517,11 +552,18 @@ specified) run these steps:
   <p>If <var>notification</var> is a <a>persistent notification</a>, then:
 
   <ol>
-   <li><p>Let <var>action</var> be the empty string.
+   <li><p>Let <var>action</var> be an empty string.
+
+   <li><p>Let <var>reply</var> be null.
 
    <li><p>If one of <var>notification</var>'s <a for=notification>actions</a> was activated by the
    user, then set <var>action</var> to that <a for=notification>action</a>'s <a for=action>name</a>.
 
+   <li><p>If one of <var>notification</var>'s <a for=notification>actions</a>
+   with type <i>'text'</i> was activated by the user, and the opportunity to
+   input a reply was provided, then set <var>reply</var> to the text entered by
+   the user during activation.
+
    <li><p>Let <var>callback</var> be an algorithm that when invoked with a <var>global</var>,
    <a lt="fire a service worker notification event named e">fires a service worker notification event</a>
    named <code>notificationclick</code> given <var>notification</var> and <var>action</var> on
@@ -666,9 +708,16 @@ enum NotificationDirection {
 };
 
 dictionary NotificationAction {
+  NotificationActionType type = "button";
   required DOMString action;
   required DOMString title;
   USVString icon;
+  DOMString? placeholder = "";
+};
+
+enum NotificationActionType {
+  "button",
+  "text"
 };
 
 callback NotificationPermissionCallback = void (NotificationPermission permission);
@@ -863,12 +912,14 @@ result of the following steps:
 <ol>
   <li><p>Let <var>frozenActions</var> be an empty list of type {{NotificationAction}}.
 
-  <li><p>For each <var>entry</var> in the <a>notification</a>'s list of
-  <a for=notification>actions</a>, perform the following steps:
+  <li><p>For each <var>entry</var> in <a>notification</a>'s <a for=notification>actions</a>:
 
   <ol>
     <li><p>Let <var>action</var> be a new {{NotificationAction}}.
 
+    <li><p>Set <var>action</var>'s {{NotificationAction/type}} to
+    <var>entry</var>'s <a for=action>type</a>.
+
     <li><p>Set <var>action</var>'s {{NotificationAction/action}} to
     <var>entry</var>'s <a for=action>name</a>.
 
@@ -878,6 +929,9 @@ result of the following steps:
     <li><p>Set <var>action</var>'s {{NotificationAction/icon}} to
     <var>entry</var>'s <a for=action>icon URL</a>.
 
+    <li><p>Set <var>action</var>'s {{NotificationAction/placeholder}} to
+    <var>entry</var>'s <a for=action>placeholder</a>.
+
     <!-- XXX IDL dictionaries are usually returned by value, so don't need to be
          immutable. But FrozenArray reifies the dictionaries to mutable JS
          objects accessed by reference, so we explicitly freeze them.
@@ -1000,11 +1054,13 @@ partial interface ServiceWorkerRegistration {
 interface NotificationEvent : ExtendableEvent {
   readonly attribute Notification notification;
   readonly attribute DOMString action;
+  readonly attribute DOMString? reply;
 };
 
 dictionary NotificationEventInit : ExtendableEventInit {
   required Notification notification;
   DOMString action = "";
+  DOMString? reply = null;
 };
 
 partial interface ServiceWorkerGlobalScope {
@@ -1087,8 +1143,10 @@ the same underlying <a>notification</a> of {{Notification}} objects already in e
 given <var>notification</var> and <var>action</var>,
 <a>fire an event</a> named <var>e</var>, using {{NotificationEvent}}, with the
 {{NotificationEvent/notification}} attribute initialized to a new
-{{Notification}} object representing <var>notification</var> and the
-{{NotificationEvent/action}} attribute initialized to <var>action</var>.
+{{Notification}} object representing <var>notification</var>, the
+{{NotificationEvent/action}} attribute initialized to <var>action</var>, and the
+{{NotificationEvent/reply}} attribute initialized to <var>reply</var>.
+
 <!-- XXX need to define at what the event is fired -->
 
 <p>The {{NotificationEvent/notification}} attribute's getter must return the
@@ -1097,6 +1155,9 @@ value it was initialized to.
 <p>The {{NotificationEvent/action}} attribute's getter must return the value it
 was initialized to.
 
+<p>The {{NotificationEvent/reply}} attribute's getter must return the value it
+was initialized to.
+
 <p>The following is the <a>event handler</a> (and its corresponding
 <a>event handler event type</a>) that must be supported as attribute by the
 {{ServiceWorkerGlobalScope}} object:
@@ -1122,6 +1183,7 @@ was initialized to.
 Addison Phillips,
 Aharon (Vladimir) Lanin,
 Alex Russell,
+Anita Woodruff,
 Anssi Kostiainen,
 Arkadiusz Michalski,
 Boris Zbarsky,