- From: Alexandre Morgaut <Alexandre.Morgaut@4d.com>
- Date: Fri, 31 May 2013 17:41:48 +0200
- To: Tobie Langel <tobie@fb.com>
- CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
On 31 mai 2013, at 09:54, Tobie Langel wrote: > The problem with standardizing user interaction with the permission layer is it completely prevents browser vendors from developing products targeted at specific market segments (e.g. you'd want super tight permission control in a device aimed at the military, but you'll want geolocation to be authorized by default in a GPS) or from coming up with innovative permission systems (e.g. whitelisting apps from certain domains, or apps trusted by friends, or automatically granting camera access when you're using a dedicated hardware button to take picture, etc.). I agree with this position Still: - for features that are not mandatory in an implementation, - if an "Always Allow" option is proposed, I think vendors should be encouraged to propose: - an easy way to remove the permission - a notification option to be sure there is no abuse of the permission I agree imposing it may be a bit unrealistic Maybe APIs involving permissions could reference to a W3C Note suggesting it Opinions? Alexandre Morgaut Wakanda Community Manager 4D SAS 60, rue d'Alsace 92110 Clichy France Standard : +33 1 40 87 92 00 Email : Alexandre.Morgaut@4d.com Web : www.4D.com
Received on Friday, 31 May 2013 15:40:15 UTC