W3C home > Mailing lists > Public > public-device-apis@w3.org > July 2011

Re: Feature Permissions Feedback

From: Robin Berjon <robin@berjon.com>
Date: Tue, 5 Jul 2011 15:14:05 +0200
Cc: public-device-apis@w3.org
Message-Id: <D052088A-88C0-449E-97BD-2DA45223A929@berjon.com>
To: Anne van Kesteren <annevk@opera.com>
Hi Anne,

thanks for the feedback. Please keep in mind that we've just inherited this spec and that what it contains is almost not at all our work. We're about to change that, though.

On Jul 5, 2011, at 10:44 , Anne van Kesteren wrote:
> On Tue, 05 Jul 2011 10:33:41 +0200, Dominique Hazael-Massieux <dom@w3.org> wrote:
>> http://dev.w3.org/2006/webapi/WebNotifications/publish/FeaturePermissions.html
> 
> If we are using "string constants" the numeric constants should be removed from the IDL and we should lowercase, potentially hyphenated, values, for consistency with e.g. the <canvas> API and XMLHttpRequest.

+1

> Furthermore, the Permissions interface should have [NoInterfaceObject] attached to it.

Agreed.

> Permissions should probably be named more consistently with other interfaces that extend Navigator, i.e. NavigatorPermissions.

Given the previous point, that's an easy change to make.

> Should this functionality be available from workers?

In as much as workers have access to multiple elevated privileges, yes. An alternative could be to specify on worker instantiation which features it is requesting.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Tuesday, 5 July 2011 13:14:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:21 GMT