Vibration API

W3C Candidate Recommendation 08 May 2012

This version:
Latest published version:
Latest editor's draft:
Previous version:
Anssi Kostiainen, Nokia


This specification defines an API that provides access to the vibration mechanism of the hosting device. Vibration is a form of tactile feedback.

Status of This Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This document represents the consensus of the group on the scope and features of the Vibration API. It should be noted that the group is aware of more advanced use cases that cannot be realised using this simpler first version. The intent is to address them in a future revision.

This document was published by the Device APIs Working Group as a Candidate Recommendation. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-device-apis@w3.org (subscribe, archives). W3C publishes a Candidate Recommendation to indicate that the document is believed to be stable and to encourage implementation by the developer community. This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than 01 July 2012. All feedback is welcome.

Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

Table of Contents

1. Introduction

This section is non-normative.

The Vibration API defines a means for web developers to programmatically provide tactile feedback in the form of vibration. The API is designed to tackle high-value use cases related to gaming, and is not meant to be used as a generic notification mechanism.

2. Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words must, must not, required, should, should not, recommended, may, and optional in this specification are to be interpreted as described in [RFC2119].

This specification defines conformance criteria that apply to a single product: the user agent that implements the interfaces that it contains.

Implementations that use ECMAScript to implement the APIs defined in this specification must implement them in a manner consistent with the ECMAScript Bindings defined in the Web IDL specification [WEBIDL], as this specification uses that specification and terminology.

3. Vibration Interface

Navigator implements Vibration;

All instances of the Navigator type are defined to also implement the Vibration interface.

interface Vibration {
    void vibrate (unsigned long time);
    void vibrate (unsigned long[] pattern);

3.1 Methods

timeunsigned long Vibration time in milliseconds.
Return type: void
patternunsigned long[] A vibration pattern represented by a list of time entries. Odd entries represent vibration time in milliseconds, even entries still periods in milliseconds between the vibrations.
Return type: void

The vibrate() method, when invoked, must run the algorithm for processing vibration patterns.

The rules for processing vibration patterns are as given in the following algorithm:

  1. If the hidden attribute [PAGE-VISIBILITY] is set to true, abort these steps.
  2. Let pattern be the value of the first argument.
  3. If pattern is 0, or an empty list, cancel the pre-existing instance of the processing vibration patterns algorithm, if any, and abort these steps.
  4. If pattern is a list, proceed to the next step. Otherwise run the following substeps:
    1. Let list be an initially empty list, and add pattern to list.
    2. Let pattern be list.
  5. If any entry of pattern exceeds an implementation-dependent limit, then the user agent may throw a NotSupportedError exception [DOM4] and abort these steps.
  6. If the length of pattern is even, then remove the last entry in pattern.
  7. If the length of pattern exceeds an implementation dependent limit, the user agent may throw a NotSupportedError exception [DOM4] and abort these steps.
  8. Cancel the pre-existing instance of the processing vibration patterns algorithm, if any.
  9. An implementation may abort the algorithm at this point.
    For example, an implementation might abort the algorithm because the user has set a preference indicating that pages at a given origin should never be able to vibrate the device, or an implementation might cap the total amount of time a page may cause the device to vibrate and reject requests in excess of this limit.
  10. For each time in pattern, run the following substeps:
    1. If the index of time is even (the earliest even entry has index 0), vibrate the device for time milliseconds.
    2. Otherwise pause [HTML5] for time milliseconds.

When the visibilitychange event [PAGE-VISIBILITY] is dispatched at the Document, the user agent must run the following steps:

  1. If the hidden attribute [PAGE-VISIBILITY] is set to true, the user agent must suppress the vibration produced by running the pre-existing instance of the processing vibration patterns algorithm, if any.
  2. If the hidden attribute [PAGE-VISIBILITY] is set to false, the user agent must restore the vibration produced by running the pre-existing instance of the processing vibration patterns algorithm, if any.

If the device does not provide a vibration mechanism, or it is disabled, the user agent must silently ignore any invocations of the vibrate() method.

4. Examples

This section is non-normative.

In the following example the device vibrates for 1 second:

// vibrate for 1 second

// or alternatively

In the following example the device vibrates for 1 second, is still for 0.5 seconds, and vibrates again for 2 seconds:

navigator.vibrate([1000, 500, 2000]);

The following example cancels any existing vibrations:


// or alternatively

A. Acknowledgements

The group is deeply indebted to Mounir Lamouri, Jonas Sicking, and the Mozilla WebAPI team in general for providing the WebVibrator prototype as an initial input.

B. References

B.1 Normative references

Anne van Kesteren; Aryeh Gregor; Ms2ger. DOM4. 5 January 2012. W3C Working Draft. (Work in progress.) URL: http://www.w3.org/TR/2012/WD-dom-20120105/
Ian Hickson; David Hyatt. HTML5. 25 May 2011. W3C Working Draft. (Work in progress.) URL: http://www.w3.org/TR/html5
J. Mann; A. Jain. Page Visibility. 26 September 2011. W3C Editor's Draft. (Work in progress.) URL: http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Internet RFC 2119. URL: http://www.ietf.org/rfc/rfc2119.txt
Cameron McCormack. Web IDL. 27 September 2011. W3C Working Draft. (Work in progress.) URL: http://www.w3.org/TR/2011/WD-WebIDL-20110927/

B.2 Informative references

No informative references.