W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2013

Re: [vibration] How to handle iframes?

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Wed, 4 Sep 2013 15:02:51 +0000
To: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
CC: "<public-device-apis@w3.org>" <public-device-apis@w3.org>
Message-ID: <050E7754-82C0-4EA3-B25A-34C521349A13@intel.com>
On Jul 31, 2013, at 6:58 PM, Michael van Ouwerkerk <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?

-Anssi
Received on Wednesday, 4 September 2013 15:04:23 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:00 UTC