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: Doug Turner <doug.turner@gmail.com>
Date: Tue, 13 Mar 2012 09:42:35 -0700
Cc: public-web-notification@w3.org
Message-Id: <926AF9DD-659A-4E2F-A6AD-5D7445B54002@gmail.com>
To: Jon Lee <jonlee@apple.com>
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".

Doug


On Mar 12, 2012, at 1:24 AM, Jon Lee wrote:

> Third thread, to add permission functions as static functions on Notification. Reposting responses:
> 
> On Mar 7, 2012, at 10:15 AM, John Gregg <johnnyg@google.com> wrote:
>> I think the biggest question that the group needs to address here is whether the Notifications spec should continue depending on the Feature Permissions for its permissions behavior (and perhaps forward these proposals there to be applied in the general sense), or should we remove that dependency and return to writing our own permissions behavior scoped to notifications?
> I believe we should not at this time depend on that spec for permissions behavior. From a general perspective, it opens the door for bad user experience, and I think this kind of API should only be available when necessary. Using the feature permissions spec makes it too easy to add new features that don't need it, and which could be handled through better API design, like in geolocation. UAs could either pummel the user with permission requests, or force the user to allow all features at once.
> 
> It seems rare to me, also, that a feature needs to obtain permission before trying to use it the first time. Because notifications are a visual medium, it is undesirable for a website to be forced to show a test notification to see if it has permission, or to request it.
> 
> Jon
Received on Tuesday, 13 March 2012 16:43:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 17 December 2012 14:48:28 GMT