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

[vibration] comment on 20130723 CR, section 4 #3 and #5

From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Date: Thu, 25 Jul 2013 10:01:53 +0200
Message-ID: <51F0DB71.50305@disruptive-innovations.com>
To: "DAP public-device-apis@w3.org" <public-device-apis@w3.org>

I have a comment about the Vibration API CR:

If I understand them correctly, section 4 items 3 and 5 say that the
requested vibration are entirely dropped in case of overflow beyond
implementation-dependent limits. So let's say an app calls

   navigator.vibrate([50, 100, 150, 100, 150]);

but the device is unable to handle a list of more than 3 values,
the device will not vibrate at all. Why that choice and not a
truncated list? Same thing for the duration of a vibration or silence,
why not a fallback to the implementation limit?
It seems to me that getting absolutely no result based on an
unpredictable device dependency is not something that developers will

Received on Thursday, 25 July 2013 08:02:22 UTC

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