- From: Peter Beverloo <notifications@github.com>
- Date: Tue, 24 Mar 2015 16:04:49 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Message-ID: <w3c/push-api/pull/131@github.com>
User agents may decide to display different UI when requesting push permission from the user if the intended use of the subscription is to only send messages which result in user visible UI, for example a Web Notification. This PR introduces this in the specification by accepting an optional property bag to the subscribe() and hasPermission() methods. This bag features a "userVisible" option that can be set to TRUE. UAs are not required to follow this UI paradigm, but when they do, they SHOULD enforce the requirement when receiving a push message. The exact tools for "user visible UI" and enforcement are left undefined as one can imagine multiple solutions for them, which we don't want to capture in the specification. You can view, comment on, or merge this pull request online at: https://github.com/w3c/push-api/pull/131 -- Commit Summary -- * Add a PushSubscriptionOptions dictionary with a userVisible option. -- File Changes -- M index.html (37) -- Patch Links -- https://github.com/w3c/push-api/pull/131.patch https://github.com/w3c/push-api/pull/131.diff --- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/131
Received on Tuesday, 24 March 2015 23:05:19 UTC