- From: Marcos Caceres <w3c@marcosc.com>
- Date: Wed, 4 Sep 2013 16:52:56 +0100
- To: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
- Cc: Kostiainen, Anssi <anssi.kostiainen@intel.com>, "<public-device-apis@w3.org>" <public-device-apis@w3.org>
On Wednesday, September 4, 2013 at 4:45 PM, Michael van Ouwerkerk wrote: > Intuitively, I would expect the vibration api to work like playing audio, which is additive. So as long as any pattern in any frame says the device must vibrate, it vibrates. I haven't fully gone through the implementation implications, but it seems doable to merge multiple patterns into one. > > We would have to change the spec to say that navigator.vibrate(0) only cancels the pattern in that frame. Patterns played from other frames are unaffected. This makes sense to me. -- Marcos Caceres
Received on Wednesday, 4 September 2013 15:53:26 UTC