E5F5 Allow notifications and actions to specify a navigable URL by annevk · Pull Request #213 · whatwg/notifications · GitHub
[go: up one dir, main page]

Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update notifications.bs
  • Loading branch information
annevk committed Nov 7, 2024
commit f4c96336d408aeaa70eb1c478b7ae0735218f05a
4 changes: 2 additions & 2 deletions notifications.bs
Original file line number Diff line number Diff line change
Expand Up @@ -560,7 +560,7 @@ platform supports activation, the user agent must (unless otherwise specified) r
<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>.
user, then set <var>action</var> to that <a for=/>notification action</a>.

<li><p>Let <var>navigationURL</var> be <var>notification</var>'s
<a for=notification>navigation URL</a>.
Expand All @@ -569,7 +569,7 @@ platform supports activation, the user agent must (unless otherwise specified) r
<p>If <var>action</var> is non-null, then set <var>navigationURL</var> to <var>action</var>'s
<a for="notification action">navigation URL</a>.

<p class=note>This intentionally makes it so that when an <a for=/>action</a>'s
<p class=note>This intentionally makes it so that when an <a for=/>notification action</a>'s
<a for="notification action">navigation URL</a> is null, it falls through to the
<code>click</code> event, providing more flexibility to the web developer.

Expand Down
Loading
0