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

Re: Vibration: throwing and pause

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 12 Apr 2013 18:19:42 +0100
Message-ID: <CADnb78gUwmfe0+-wKNJ1BQfca4eryWFM2mpLmJTvYRW1ur24Ew@mail.gmail.com>
To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>
On Fri, Apr 12, 2013 at 6:12 PM, Kostiainen, Anssi
<anssi.kostiainen@intel.com> wrote:
> On Apr 11, 2013, at 5:24 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> Since there are so many opportunities for the UA to just say "fuck it"
>> having this method sometimes maybe throw seems more like a burden than
>> an actual help to developers. I recommend not throwing at all.
> This feature is shipping in Firefox for Android and Firefox OS.
> Have you received feedback from developers that this is a burden?

No, but given that the user agent may terminate either way (including
without exception), it is better not to throw, especially as this it
is implementation-dependent. You only want to throw if it's traceable
to a clear developer error, here it's not at all clear why.

Also, I think the IDL should say "(unsigned long or sequence<unsigned
long>) pattern"

>> Also, "pause"?! Is that intentional?
> This was fixed in the Editor's Draft, see "spin the event loop":
>   http://dev.w3.org/2009/dap/vibration/

So why does that spin the event loop? Having this method be
synchronous seems really bad.

Received on Friday, 12 April 2013 17:20:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:53 UTC