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

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

From: Jon Lee <jonlee@apple.com>
Date: Mon, 12 Mar 2012 01:24:58 -0700
Message-id: <E7C55729-5B43-46C5-90D0-7F2581810A1B@apple.com>
To: public-web-notification@w3.org
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 Monday, 12 March 2012 08:25:46 GMT

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