Re: [vibration] How to handle iframes?

Is there any precedent for restricting to top level browsing context? It
would make the API less useful, so it doesn't seem like a very attractive
solution to me.

Regards,

Michael


On Wed, Sep 4, 2013 at 4:02 PM, Kostiainen, Anssi <
anssi.kostiainen@intel.com> wrote:

> 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