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

Re: Vibration: throwing and pause

From: Justin Lebar <justin.lebar@gmail.com>
Date: Tue, 16 Apr 2013 11:07:25 +0200
Message-ID: <CAFWcpZ7H+QMEH=9ybbEfQGp7oqqqAG0tOhFo0Yjd19uWVcggbA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
On Tue, Apr 16, 2013 at 10:57 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Tue, Apr 16, 2013 at 9:14 AM, Justin Lebar <justin.lebar@gmail.com> wrote:
>> I don't think we want to return false when the pattern is 0, the empty
>> list, or if the device doesn't support vibration.  At the very least,
>> this exposes to pages whether the device supports vibration, which I
>> thought was something we wanted to avoid.  But also, vibrate([])
>> "succeeds" if it gets to step (9), so it should return true, I think.
> It seems better to expose that via the API than have developers rely
> on UA-sniffing.

When we wrote this API we were worried about fingerprinting.  If we're
not worried about this anymore, then that's fine.  I don't have a
strong opinion.
Received on Tuesday, 16 April 2013 09:08:18 UTC

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