- From: Marcos Caceres <w3c@marcosc.com>
- Date: Wed, 4 Sep 2013 16:07:43 +0100
- To: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Cc: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>, "<public-device-apis@w3.org>" <public-device-apis@w3.org>
On Wednesday, September 4, 2013 at 4:02 PM, Kostiainen, Anssi wrote: > On Jul 31, 2013, at 6:58 PM, Michael van Ouwerkerk <mvanouwerkerk@chromium.org (mailto:mvanouwerkerk@chromium.org)> wrote: > > > Apologies for reposting. There was no reply to my previous email, and I suspect it might be because I didn't phrase the subject correctly. Here goes again :-) > > > > Hi, I'm implementing the Vibration API in Blink and Chromium and noticed that the expected behavior is not explicitly specified for iframes. > > > > Should the patterns be additive - vibration only stops when all patterns in all iframes have fully run. This is kind of like playing sounds from multiple sources at the same time, they can overlap. > > > > Or should we be more conservative and stop vibration when any pattern in any iframe ends, or navigator.vibrate(0) is called anywhere? > > Sorry for a delayed reply. > > Perhaps we should restrict this to the top-level browsing context, otherwise cancel. > > WDYT? I think that would be confusing and make the API harder to use. Imagine that I could have a game running inside an iframe, with the menu items, etc. in the top level browsing context. -- Marcos Caceres
Received on Wednesday, 4 September 2013 15:08:14 UTC