W3C home > Mailing lists > Public > public-web-notification@w3.org > March 2012

Re: static permission functions on Notification (was Feedback from Safari on Web Notifications)

From: Jon Lee <jonlee@apple.com>
Date: Tue, 13 Mar 2012 10:33:05 -0700
Cc: public-web-notification@w3.org
Message-id: <014AF96A-573A-4242-B389-5DE8DEFF06F1@apple.com>
To: Doug Turner <doug.turner@gmail.com>

On Mar 13, 2012, at 9:42 AM, Doug Turner wrote:

> Hi Jon,
> I am not really sure what I think about Notification's using Feature permissions or not.  However, I do believe that we need something that does pre-authorization.  
> For example, with Geo, the user is actively interacting with a document.  in Google Maps, there is a button in the UI that you press which kicks off a geo request.  With Notifications, it is different.  In this model, you tell a website "please notify when something happens".  The user typically isn't interacting a with the document at all.  They may even be in another application or away from their device/computer.  I do hope that the first notification isn't "this background application wants to ask you for permission to notify you when something happens".

I didn't mean to imply that we should get rid of permissions altogether, just whether those functions apply only to Notifications, rather than generalizing it for any feature. I understand that because of the notification's visual nature, you don't want to send a test notification to see if you have permission, or to request it.

Received on Tuesday, 13 March 2012 17:37:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:13 UTC