W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: [gamepad] Haptic Feedback/Controller Vibration

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Fri, 4 Apr 2014 13:45:59 +0000
To: Ted Mielczarek <ted@mozilla.com>
CC: Brandon Jones <bajones@google.com>, Patrick Martin <patrick.martin.r@gmail.com>, Webapps WG <public-webapps@w3.org>
Message-ID: <AF4412E2-58F1-4A25-B514-F6491B28D907@intel.com>
Hi Ted,

On 03 Apr 2014, at 18:34, Ted Mielczarek <ted@mozilla.com> wrote:

> On 3/24/2014 1:04 AM, Brandon Jones wrote:
>> Mozilla has played around with gamepad vibration a bit already: https://bugzilla.mozilla.org/show_bug.cgi?id=680289
>> There's been some mixed messages, but so far the basic idea seems to be to either extend the existing Vibration API to handle multiple motors (and presumably associate it back to a specific pad) or to add a very similar looking "vibrate" function to the gamepad API. Something like:
>> 
>> vibrate(int motorIndex, float intensity);
> Our primary intention there was simply "don't reinvent the wheel if you don't have to". If we can map controller vibration to the existing Vibration API that saves us having to do a whole bunch of spec work ourselves. Given the extra complexity of having multiple vibration motors at different frequencies it may be unavoidable though. I think it's still worth pursuing, we should at least talk to the people behind the Vibration API to see if we can leverage their work.

In the initial versions of the spec we indeed considered such reuse. Here’s my recent summary:

  http://lists.w3.org/Archives/Public/public-device-apis/2014Apr/0002.html

That said, we can start work on a Level 2 spec if good new use cases emerge, for example, in the context of the Gamepad API. Feel free to chime in on the public-device-apis for follow-ups.

Thanks,

-Anssi 
Received on Friday, 4 April 2014 13:49:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:23 UTC