- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Wed, 4 Sep 2013 15:57:41 +0000
- To: "public-device-apis@w3.org" <public-device-apis@w3.org>, "Michael van Ouwerkerk" <mvanouwerkerk@chromium.org>
On Sep 4, 2013, at 6:45 PM, Michael van Ouwerkerk <mvanouwerkerk@chromium.org> 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. > > I've gone over the Geolocation API spec a number of times recently, and I don't remember it saying anything about restricting to the top level frame. This was just a proposal sent to the mailing list IIRC, so it never landed to the spec. > What do you think? Looks good to me. All - do you have concerns with Michael's proposal? If I hear no concerns, I'm happy to update the spec. -Anssi
Received on Wednesday, 4 September 2013 15:58:38 UTC