W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2014

Re: Vibration

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Fri, 14 Nov 2014 17:57:00 +0000
To: Anne van Kesteren <annevk@annevk.nl>
CC: Mounir Lamouri <mounir@lamouri.fr>, www-archive <www-archive@w3.org>, Device APIs Working Group <public-device-apis@w3.org>
Message-ID: <97D13CCE-60E0-473D-AB08-8F82F6067C2C@intel.com>
> On 13 Nov 2014, at 19:34, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Thu, Oct 9, 2014 at 3:32 PM, Kostiainen, Anssi
> <anssi.kostiainen@intel.com> wrote:
>> On 09 Oct 2014, at 15:46, Anne van Kesteren <annevk@annevk.nl> wrote:


>> We tried to keep the scope as tight as possible and did not add any extras, thus not much to do differently.
> Okay.
> I was wondering if you could provide the following features.
> * A dedicated name for the method argument, so that I can use it
> elsewhere. E.g. VibratePattern or some such.
> * A standalone algorithm that performs the additional validation
> required and normalizes the input.
> * A standalone algorithm that performs the actual vibration.
> This should make it possible to introduce notifications that vibrate
> while reusing the vibration infrastructure the Vibration API
> implicitly (hopefully soon explicitly) provides.

I updated the Editor's Draft to provide the following hooks:


Please help me fix any spec bugs, and let me know if you need something else to make the spec more reusable.

Btw. I'm happy to see Notifications API get more capable, integrate with other nifty features on the Web Platform such as vibration ;-)


Received on Friday, 14 November 2014 17:57:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:14 UTC