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 08:42:13 +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: <DA22857AC9F15C469BB47FE88C0201292A92CAC1@SZXEML510-MBS.china.huawei.com>
> -----Original Message-----
> From: Anssi Kostiainen [mailto:anssi.kostiainen@nokia.com]
> Sent: Wednesday, November 23, 2011 4:36 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.07, ext Deepanshu gautam wrote:
> 
> > Please refer to my following posts (for which I didn't get any
> response)
> >
> > http://lists.w3.org/Archives/Public/public-device-
> apis/2011Nov/0181.html
> >
> > The use case is simple: As a developer I want to know whether the
> Vibrator is ON or OFF (at native layer), before trying to vibrate my
> app. And, Since I'm using DAP VibrationAPI I expect that same API to
> provide me with this functionality.
> 
> You cannot always expect feature parity between Web APIs and native
> APIs due to different security models employed.
[DG] What security breach you foresee here? I heard that fingerprinting is not an issue here.
> 
> -Anssi
Received on Wednesday, 23 November 2011 08:43:33 GMT

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