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

Re: [vibration] How to handle iframes?

From: <Frederick.Hirsch@nokia.com>
Date: Wed, 4 Sep 2013 22:21:47 +0000
To: <anssi.kostiainen@intel.com>
CC: <Frederick.Hirsch@nokia.com>, <public-device-apis@w3.org>, <mvanouwerkerk@chromium.org>
Message-ID: <1CB2E0B458B211478C85E11A404A2B2702DF06CC@008-AM1MPN1-034.mgdnok.nokia.com>
This seems remarkably sensible - if anything wants to vibrate, it vibrates regardless of how many etc. Seems simple and understandable.  :)

thanks Michael.

regards, Frederick

Frederick Hirsch
Nokia



On Sep 4, 2013, at 11:57 AM, ext Kostiainen, Anssi wrote:

> 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 22:40:26 UTC

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