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

DAP-ISSUE-150: Should vibration be additive when multiple instances, e.g. iframes [Vibration API]

From: Device APIs Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 04 Sep 2013 15:54:18 +0000
Message-Id: <E1VHFPO-0001PB-Ac@nelson.w3.org>
To: public-device-apis@w3.org
DAP-ISSUE-150: Should vibration be additive when multiple instances, e.g. iframes [Vibration API]

http://www.w3.org/2009/dap/track/issues/150

Raised by: Frederick Hirsch
On product: Vibration API

raised by Michael van Ouwerkerk

http://lists.w3.org/Archives/Public/public-device-apis/2013Jul/0055.html

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?

Regards,

Michael van Ouwerkerk
Received on Wednesday, 4 September 2013 15:54:23 UTC

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