From 8e39f864d2fbc203ba00c3f8833c5cdfaf3499ed Mon Sep 17 00:00:00 2001
From: Peter Beverloo <peter@chromium.org>
Date: Fri, 20 Oct 2017 14:18:29 +0100
Subject: [PATCH] Add a warning about the reliability of the notificationclose
 event

Not all platforms dispatch an event to the applications (e.g. the user
agent) when a notification is dismissed, or only do so in a subset of
cases. This means that the `notificationclose` event is a best-effort
event. It adds significant value to the developer, as dismissal is a
powerful (yet complicated) signal, so user agents should still make an
effort to support it where they can.

Fixes #109
---
 notifications.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/notifications.bs b/notifications.bs
index 33416ba..ab8f92a 100644
--- a/notifications.bs
+++ b/notifications.bs
@@ -582,6 +582,10 @@ must be run.
   <li><p>Remove <var>notification</var> from the <a>list of notifications</a>.
 </ol>
 
+<p class="warning">Because not all notification centers reliably dispatch an event when a
+notification is closed, the <code>notificationclose</code> event will be delivered on a best-effort
+basis. User agents should aim to support the event whenever possible.
+
 
 <h3 id=displaying-notification>Displaying notifications</h3>