Allow notifications and actions to specify a navigable URL

This makes notifications more declarative by not requiring explicit handling of the clicks by the web application.

Author: annevk

notifications.bs

@@ -48,9 +48,6 @@ representation of something that happened, such as the delivery of a message.
 <p>A <a>notification</a> has an associated
 <dfn for=notification id=concept-title>title</dfn> which is a string.
 
-<p>A <a>notification</a> has an associated
-<dfn for=notification id=body>body</dfn> which is a string.
-
 <p>A <a>notification</a> has an associated
 <dfn for=notification id=concept-direction>direction</dfn> which is "<code>auto</code>",
 "<code>ltr</code>", or "<code>rtl</code>".
@@ -59,6 +56,12 @@ representation of something that happened, such as the delivery of a message.
 <dfn for=notification id=concept-language>language</dfn> which is a string
 representing either a valid BCP 47 language tag or the empty string.
 
+<p>A <a>notification</a> has an associated <dfn for=notification id=body>body</dfn> which is a
+string.
+
+<p>A <a>notification</a> has an associated <dfn for=notification>URL</dfn> which is null or a
+<a for=/>URL</a>. It is initially null.
+
 <p>A <a>notification</a> has an associated
 <dfn for=notification id=tag>tag</dfn> which is a string.
 
@@ -129,12 +132,15 @@ support these features might ignore them.
 for an end user. Each <a for=/>action</a> has an associated:
 
 <dl>
- <dt><dfn for=action id=action-title>title</dfn>
+ <dt><dfn for=action id=action-name>name</dfn>
  <dd>A string.
 
- <dt><dfn for=action id=action-name>name</dfn>
+ <dt><dfn for=action id=action-title>title</dfn>
  <dd>A string.
 
+ <dt><dfn for=action>URL</dfn>
+ <dd>Null or a <a for=/>URL</a>. It is initially null.
+
  <dt><dfn for=action>icon URL</dfn>
  <dd>Null or a <a for=/>URL</a>. It is initially null.
 
@@ -211,6 +217,24 @@ string <var>title</var>, {{NotificationOptions}} <a for=/>dictionary</a> <var>op
  <li><p>Set <var>notification</var>'s <a for=notification>body</a> to
  <var>options</var>["{{NotificationOptions/body}}"].
 
+ <li>
+  <p>If <var>options</var>["{{NotificationOptions/url}}"] <a for=map>exists</a>:
+
+  <ol>
+   <li><p>Let <var>url</var> be the result of <a lt="URL parser">parsing</a>
+   <var>options</var>["{{NotificationOptions/url}}"] using <var>baseURL</var>.
+
+   <li>
+    <p>If <var>url</var> is not failure:
+
+    <ol>
+     <li><p>If <var>url</var>'s <a for=url>origin</a> is not <a>same origin</a> with
+     <var>notification</var>'s <a for=notification>origin</a>, then <a>throw</a> a {{TypeError}}.
+
+     <li><p>Set <var>notification</var>'s <a for=notification>URL</a> to <var>url</var>.
+    </ol>
+  </ol>
+
  <li><p>Set <var>notification</var>'s <a for=notification>tag</a> to
  <var>options</var>["{{NotificationOptions/tag}}"].
 
@@ -266,6 +290,24 @@ string <var>title</var>, {{NotificationOptions}} <a for=/>dictionary</a> <var>op
    <li><p>Set <var>action</var>'s <a for=action>title</a> to
    <var>entry</var>["{{NotificationAction/title}}"].
 
+   <li>
+    <p>If <var>entry</var>["{{NotificationAction/url}}"] <a for=map>exists</a>,
+
+    <ol>
+     <li><p>Let <var>url</var> be the result of <a lt="URL parser">parsing</a>
+     <var>entry</var>["{{NotificationAction/url}}"] using <var>baseURL</var>.
+
+     <li>
+      <p>If <var>url</var> is not failure:
+
+      <ol>
+       <li><p>If <var>url</var>'s <a for=url>origin</a> is not <a>same origin</a> with
+       <var>notification</var>'s <a for=notification>origin</a>, then <a>throw</a> a {{TypeError}}.
+
+       <li><p>Set <var>action</var>'s <a for=action>URL</a> to <var>url</var>.
+      </ol>
+    </ol>
+
    <li><p>If <var>entry</var>["{{NotificationAction/icon}}"] <a for=map>exists</a>, then
    <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
@@ -527,14 +569,39 @@ interpreted as a language tag. Validity or well-formedness are not enforced. [[!
 platform supports activation, the user agent must (unless otherwise specified) run these steps:
 
 <ol>
+ <li><p>Let <var>action</var> be null.
+
+ <li><p>If one of <var>notification</var>'s <a for=notification>actions</a> was activated by the end
+ user, then set <var>action</var> to that <a for=/>action</a>.
+
+ <li><p>Let <var>url</var> be <var>notification</var>'s <a for=notification>URL</a>.
+
+ <li>
+  <p>If <var>action</var> is non-null, then set <var>url</var> to <var>action</var>'s
+  <a for=action>URL</a>.
+
+  <p class=note>This intentionally makes it so that when an <a for=/>action</a>'s
+  <a for=action>URL</a> is null, it falls through to the <code>click</code> event, providing more
+  flexibility to the web developer.
+
+ <li>
+  <p>If <var>url</var> is non-null:
+
+  <ol>
+   <li><p><a>Create a fresh top-level traversable</a> given <var>url</var>.
+   <!-- XXX Should maybe set userInvolvement correctly here? -->
+
+   <li><p>Return.
+  </ol>
+
  <li>
   <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>actionName</var> be the empty string.
 
-   <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=/>action</a>'s <a for=action>name</a>.
+   <li><p>If <var>action</var> is non-null, then set <var>actionName</var> to <var>action</var>'s
+   <a for=action>name</a>.
 
    <li><a>Fire a service worker notification event</a> named "<code>notificationclick</code>" given
    <var>notification</var> and <var>action</var>.
@@ -622,6 +689,7 @@ interface Notification : EventTarget {
   readonly attribute NotificationDirection dir;
   readonly attribute DOMString lang;
   readonly attribute DOMString body;
+  readonly attribute USVString url;
   readonly attribute DOMString tag;
   readonly attribute USVString image;
   readonly attribute USVString icon;
@@ -641,6 +709,7 @@ dictionary NotificationOptions {
   NotificationDirection dir = "auto";
   DOMString lang = "";
   DOMString body = "";
+  USVString url;
   DOMString tag = "";
   USVString image;
   USVString icon;
@@ -669,6 +738,7 @@ enum NotificationDirection {
 dictionary NotificationAction {
   required DOMString action;
   required DOMString title;
+  USVString url;
   USVString icon;
 };
 
@@ -824,6 +894,16 @@ return the <a>maximum number of actions</a> supported.
 <p>The <dfn attribute for=Notification><code>body</code></dfn> getter steps are to return
 <a>this</a>'s <a>notification</a>'s <a for=notification>body</a>.
 
+<p>The <dfn attribute for=Notification><code>url</code></dfn> getter steps are:
+
+<ol>
+ <li><p>If <a>this</a>'s <a>notification</a>'s <a for=notification>URL</a> is null, then return the
+ empty string.
+
+ <li><p>Return <a>this</a>'s <a>notification</a>'s <a for=notification>URL</a>,
+ <a lt="URL serializer">serialized</a>.
+</ol>
+
 <p>The <dfn attribute for=Notification><code>tag</code></dfn> getter steps are to return
 <a>this</a>'s <a>notification</a>'s <a for=notification>tag</a>.
 
@@ -896,6 +976,10 @@ then return null.
    <li><p>Set <var>action</var>["{{NotificationAction/title}}"] to <var>entry</var>'s
    <a for=action>title</a>.
 
+   <li><p>If <var>entry</var>'s <a for=action>URL</a> is non-null, then set
+   <var>action</var>["{{NotificationAction/url}}"] to <var>entry</var>'s <a for=action>URL</a>,
+   <a lt="URL serializer">serialized</a>.
+
    <li><p>If <var>entry</var>'s <a for=action>icon URL</a> is non-null, then set
    <var>action</var>["{{NotificationAction/icon}}"] to <var>entry</var>'s
    <a for=action>icon URL</a>, <a lt="URL serializer">serialized</a>.
@@ -937,7 +1021,7 @@ not.onclick = function() { displaySong(this); };</pre>
 
 <p>Here a service worker shows a notification with a single "Archive" <a for=/>action</a>, allowing
 users to perform this common task from the notification without having to open the website (for
-example the, notification platform might show a button on the notification). The user can also
+example, the notification platform might show a button on the notification). The user can also
 activate the main body of the notification to open their inbox.
 
 <pre class=example id=example-50e7c86c>