W3C home > Mailing lists > Public > public-web-mobile@w3.org > February 2014

Re: RfC: LCWD of Vibration API; deadline March 4

From: Peter Beverloo <beverloo@google.com>
Date: Wed, 12 Feb 2014 13:58:00 +0000
Message-ID: <CALt3x6nxVtLLeLjeb16urtEs8kW5PB3NovRK+QpsRcRW8=T53w@mail.gmail.com>
To: Marcos Caceres <w3c@marcosc.com>
Cc: Terence Eden <Terence.Eden@telefonica.com>, Web and Mobile IG <public-web-mobile@w3.org>
On Wed, Feb 12, 2014 at 1:40 PM, Marcos Caceres <w3c@marcosc.com> wrote:
>
> On Wednesday, February 12, 2014 at 1:37 PM, Terence Eden wrote:
>
> > I'd be interested in two things.
> > 1) Getting the max length of patterns and vibration times from a device.
> There seems to be no way to do this at present.

Can you explain a bit more what you would do with that?
>

The maximum length and duration of a vibration pattern are defined to be
implementation specific.  In Chrome we adhere to a maximum length of 99
entries, and a maximum total duration of 10 seconds.  Firefox has a
configurable maximum length, defaulting to 128 entries, and a maximum
duration of 10 seconds, which is configurable as well.

One completely unimportant use case I can imagine is using a device's
vibrator to "play a song".  Remember those awesome buzz-tones from the late
90s? :-).

> 2) Future proposals to indicate the *intensity* of vibration.
>
> Intensity control would be nice.
>

Which platforms would support setting the vibration's intensity?  The
Android APIs do not, and vibrations on iOS are initiated through their
audio system, which don't support intensity either.  This can easily be
worked around by the developer by vibrating [25, 10, 25, 10, 25] instead of
[95].

Peter
Received on Wednesday, 12 February 2014 13:58:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:59:03 UTC