- From: Justin Lebar <jlebar@mozilla.com>
- Date: Mon, 7 Nov 2011 13:45:24 -0500
- To: João Eiras <joaoe@opera.com>
- Cc: public-device-apis@w3.org
As in navigator.vibrator.vibrate()? I don't understand why this is better than navigator.vibrate(). Why can't the gamepad API expose a method which matches navigator.vibrate()? -Justin On Mon, Nov 7, 2011 at 1:03 PM, João Eiras <joaoe@opera.com> wrote: > > Hi. > > The vibrator API's WebIDL [1] should not expose the two methods directly in > the navigator object. > > Instead it should be in a separate interface, so it can be implemented as a > singleton API in the window/navigator object for a mobile device like a > phone, or can be implemented on top of the gamepad object whenever the > gamepad APIs moves forward, to feed vibration back to the controller. > > Thanks. > > [1] http://dev.w3.org/2009/dap/vibration/ > >
Received on Monday, 7 November 2011 18:46:13 UTC