- From: Deepanshu gautam <deepanshu.gautam@huawei.com>
- Date: Wed, 23 Nov 2011 08:07:02 +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>
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. Regards Deepanshu Gautam Service Standards, Huawei Software T: +86 25 5260008 M: +86 135 85147627 > -----Original Message----- > From: Anssi Kostiainen [mailto:anssi.kostiainen@nokia.com] > Sent: Wednesday, November 23, 2011 3:57 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 3.48, ext Deepanshu gautam wrote: > > > I'm wondering if I should consider this silence as agreement for my > proposal in the thread below :-) > > > > My proposal: To have function like VibStatus() returning "VibON" and > "VibOFF". To let pages know whether the vibrator in ON or OFF > > To me it seems we haven't reached consensus on this. > > See my initial proposal: > > http://lists.w3.org/Archives/Public/public-device- > apis/2011Nov/0152.html > > And Robin's reply: > > http://lists.w3.org/Archives/Public/public-device- > apis/2011Nov/0158.html > > We haven't unearthed any use cases yet that would require explicit > control over the on/off toggle by a web app. Please let us know if you > have any. > > -Anssi
Received on Wednesday, 23 November 2011 08:09:33 UTC