W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2013

Re: [Permissions] Notification on Device API Access

From: Alexandre Morgaut <Alexandre.Morgaut@4d.com>
Date: Mon, 3 Jun 2013 11:42:11 +0200
To: Robin Berjon <robin@w3.org>
CC: Tobie Langel <tobie@fb.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <BA7CB57B-4C7D-4F22-BFC2-6EEEA5F0D02B@4d.com>

On 3 juin 2013, at 10:43, Robin Berjon wrote:

> I agree that it's a reasonable thing to expect from an implementation.
> But the problem is that with such a document you enter UI
> specifications. And implementers tend to ignore those.

Well, in my initial mail I agree that I talked about a checkbox or multiple buttons.
Those had to be taken as UI examples to provide the option, that's why I was less explicit in the second mail.
So I don't mind if implementors find any other way to propose it as long as such options are proposed.

> There have been
> attempts to write such documents, notably for situations where it could
> really be important to have some user-visible interoperability (notably
> for security-related UI, such as telling the user that she is navigating
> an HTTPS site) but they have all failed.

I have another HTTP Authentication related concern I'd love to bring back too
But I know it may not be easy neither

> So before jumping into writing anything, it's well worth making sure
> that the resulting document will actually be useful, read, applied, etc.

agree

> I guess the important question is: what do you hope to make happen with
> such a document that implementers wouldn't already do because they care
> about the experience that their users have?

My hope:
- is better privacy protection for the user
- better adoption of the app for the developer, as user could be less afraid

But this hope does not belong to a specific format of document as long as most implementors take the concern into account.
W3C working groups seemed to be a good start to me for such discussion as most browser vendors participate to those.
I may publish a bug on each browser vendor issue tracker but what if a new one comes in, more specifically a business specific one we may not be aware of... A reference document may help, and, unless governments provide one of their own regarding privacy issue, the W3C might help in this area.








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 Monday, 3 June 2013 09:40:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:59 UTC