[w3c/push-api] APA WG comment: ability to pause notifications (#259)

The Accessible Platform Architectures (APA) Working Group review of Push API suggests that additional feature support is required by emerging use cases.

APA believes a mechanism is needed to allow applications to temporarily block any push notifications or events. All such notifications or events should be queued until the application requesting temporary blocking has cleared the blocking request.

Two use cases supporting such a feature:

==Use Case #1: time-critical tasks

A user engaged in a financial transaction at the point of making (or receiving) payment should not be interrupted by unrelated notifications and events. This is especially important for persons with disabilities
relying on assistive technology, but is also relevant to all users of emerging web payments specifications.

==Use Case #2: reduce interruptions

Users need the ability to interact with certain web content without automated updates that might cause presented content to update in an adverse manner.

This might be satisfied by allowing temporary pauses in push events, or by controlling a minimum time interval between push events.

For more on this use case see the comment at: http://lists.w3.org/Archives/Public/public-apa/2017May/0026.html

[APA tracking of Push API comments](https://www.w3.org/WAI/APA/wiki/Push_API)

-- 
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/259