Re: [w3c/push-api] User preference for timing (#257)

Hi Ted, thank you for your report! The Push API is a communication protocol and defines means through which a message could _reach_ the user. The developer then has to use other features to _display_ the content to the user, if at all necessary. To give some example options:

- Displaying a notification. This is the common case, where the [Notifications API](https://notifications.spec.whatwg.org) is used to display the notification. This often means that display, and options thereof, are delegated to the underlying operating system.

- Updating an opened page. Notably, displaying the received message in an already opened chat window, or comment stream. This, as well as the pursuing layout changes, is entirely the developer's doing.

- Update the cache. In this case nothing has to be displayed to the user at all.

Specifically to your question, I feel that it's a shared responsibility between the user agent (who choses a notification center) and the operating system (who usually provides one) to ensure displayed notifications are sufficiently accessible. However, since the act of _displaying_ content is out of scope of this specification, I'm not sure whether adding a note would be sufficiently beneficial.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/257#issuecomment-300535632