- From: Jake Archibald <jakearchibald@google.com>
- Date: Thu, 21 Mar 2013 09:03:38 +0000
- To: Jon Lee <jonlee@apple.com>
- Cc: Anne van Kesteren <annevk@annevk.nl>, WG <public-web-notification@w3.org>
On Thu, Mar 21, 2013 at 8:37 AM, Jon Lee <jonlee@apple.com> wrote: > It seems odd that a web author would post notifications without caring about whether the user has opted in. The callback isn't needed to do this, there's Notification.permission. You only need the callback to know when the user has dealt with the permission request. Even then, updating the UI at this point isn't reliable, as presumably a user agent may allow the user to later revoke notification permissions, imagine a button on the notification like "Prevent further notifications from this site" like some browsers do with alert(), or perhaps even "Prevent notifications for 10 minutes". Both cases are going to change permissions without notifying the page, the latter is going to make 2 changes. With that in mind, would we be better off with a "permissionchange" event? Can a constructor be an EventTarget?
Received on Friday, 22 March 2013 13:22:54 UTC