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

RE: [vibration] Preliminary thoughts on the vibrator spec

From: Deepanshu gautam <deepanshu.gautam@huawei.com>
Date: Wed, 23 Nov 2011 09:18:09 +0000
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Cc: Robin Berjon <robin@berjon.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Message-id: <DA22857AC9F15C469BB47FE88C0201292A92CB05@SZXEML510-MBS.china.huawei.com>

> -----Original Message-----
> From: Anssi Kostiainen [mailto:anssi.kostiainen@nokia.com]
> Sent: Wednesday, November 23, 2011 5:00 PM
> To: Deepanshu gautam
> Cc: Robin Berjon; public-device-apis@w3.org public-device-apis@w3.org
> Subject: Re: [vibration] Preliminary thoughts on the vibrator spec
> 
> On 23.11.2011, at 10.42, ext Deepanshu gautam wrote:
> 
> > [DG] What security breach you foresee here? I heard that
> fingerprinting is not an issue here.
> 
> The proposed functionality can be used to annoy users. As a user, I
> want to be in control of whether my device is able to vibrate (or make
> sounds, or annoy me otherwise). 
[DG] I'm not proposing to enable Vibration automatically (without user consent). It is just to allow Web Apps to know whether Vibrator is OFF and then notify UA. Which may then ask user to switch it on (however, that part is out-of-scope here). This will avoid UA/OS/device to keep monitoring if some unavailable functionality is being used and then notify user. The better way would be for *app* to say "Hey I want to use XXX would you like to switch it on" and user may decide to switch it on for that particular session, forever, forever for that particular application etc. 
>And I want to control that globally similarly to sound level, not on per web app basis.
[DG] User experience will be same. Whether app tell UA (that I want to user an unavailable function) or UA finds it by itself (before notifying user) is transparent to user.
> 
> -Anssi
Received on Wednesday, 23 November 2011 09:20:19 GMT

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