Browser engine support

The following table lists browser engines, not individual browsers. Chromium-based browsers (Chrome, Edge, Opera, Samsung Internet, WebView Android, etc.) all share the Blink engine and are counted as a single implementation.

Historical implementation experience

In addition to the current implementation experience above, the Vibration API has a history of implementation in engines that no longer support it.

WebKit (EFL port, 2012–2017)

Samsung engineer Kihong Kwon landed initial Vibration API support in WebKit in 2012 for the EFL port, which was used on Samsung Tizen devices. The EFL port enabled the feature (ENABLE_VIBRATION PUBLIC ON in Source/cmake/OptionsEfl.cmake) and received bug fixes through 2015.

The EFL port was removed from the WebKit mainline in February 2017. In May 2017, the Vibration API code itself was removed (Bug 171766, changeset 216696). The removal bug states: "Not enabled by any ports. Tests are skipped by all ports. Unmaintained code."

A separate fork, ewebkit/webkit, retains the Vibration API code but has not been updated since July 3, 2017. The Tizen devices that used EFL WebKit are no longer in production.

No Web Platform Test results exist for any EFL WebKit-based browser.

Source code verification (April 2026)

The following was verified by searching and reading the source code of each engine. To reproduce, clone each repository and search for the files and identifiers listed below (e.g., using grep -r or your editor's search).

• Blink (chromium/src): VibrationController is implemented in third_party/blink/renderer/modules/vibration/vibration_controller.cc. The vibrate() method requires sticky user activation (HasStickyUserActivation()) and blocks calls from cross-origin iframes (IsCrossOriginToNearestMainFrame()) and fenced frames. The WebIDL is in third_party/blink/renderer/modules/vibration/navigator_vibration.idl.
• Gecko (mozilla-central): The vibrate() WebIDL binding is in dom/webidl/Navigator.webidl, gated on the dom.vibrator.enabled preference. That preference defaults to false in modules/libpref/init/StaticPrefList.yaml. No platform-specific override exists in mobile/android/app/geckoview-prefs.yaml or elsewhere. The HAL implementation remains in hal/android/AndroidHal.cpp (Vibrate()) and hal/fallback/FallbackVibration.cpp (no-op stub for desktop), but is unreachable with the preference disabled.
• WebKit (WebKit/WebKit): No vibrate() method in any IDL file. No VibrationController, NavigatorVibration, or ENABLE_VIBRATION flag anywhere in the source tree. The API is entirely absent.

Gecko (Firefox, 2012–2024)

Firefox supported the Vibration API from version 16 (October 2012) through version 128 (desktop). On Android, vibration was disabled starting in version 79 (July 2020): the API remained present and navigator.vibrate() returned true when the window was visible, but no haptic feedback was produced (Bug 1653318). The feature was not re-enabled due to abuse concerns.

Firefox Desktop removed the API entirely in version 129 (August 6, 2024, Bug 1900037).

Test results

The following tests verify conformance to [[vibration]].

For the latest automated test results, visit wpt.fyi/results/vibration.

Status legend

PASS

The test ran successfully and the implementation conforms to the specification.

FAIL

The test ran and the implementation does not conform to the specification, or the API is not exposed.

Automated test results

Results from wpt.fyi, last verified April 9, 2026. Since Firefox 129 (August 2024), the API is no longer exposed on any Firefox platform (see Historical implementation experience).

Manual test results

Manual tests verify that the vibration mechanism is actually triggered on the device. These tests cannot be automated. Tests were conducted on 2024-06-08 (see w3c/vibration#33) against the following browser versions:

• Chrome for Android 125.0.6422 (Blink engine)
• Firefox for Android 126.0.1 (Gecko engine)
• Safari on iOS 17.4.1 (WebKit engine)

Is each feature of the current specification implemented, and how is this demonstrated?

All features of [[vibration]] are implemented in the Blink engine (Chrome for Android, Chrome desktop, Edge, and other Chromium-based browsers). This is demonstrated through the automated and manual WPT results above. No other engine provides a functional implementation.

Are there independent interoperable implementations of each feature?

No. Only one browser engine (Blink) provides a functional implementation. Firefox removed support in version 129 (August 6, 2024); the API is now disabled on all Firefox platforms, including Android (see Historical implementation experience). WebKit has never shipped the API and formally opposes it.

Are the implementations by different, independent developers?

The Chromium-based implementations (Chrome, Edge, Opera, Samsung Internet, etc.) share the same Blink engine codebase and are not independent of each other. They represent a single implementation.

Are the implementations deployed on production systems?

Yes, in Chromium-based browsers. Not in Firefox (removed) or Safari (never shipped).

Are there reports of difficulties or problems with implementation?

Yes. Chrome introduced cross-origin iframe restrictions (v55) and user gesture requirements (v60) in response to widespread abuse of the API. A manual review of sites calling navigator.vibrate() found usage dominated by notification emulation, ad-related scripts, and patterns now blocked by Chrome's mitigations. Chrome use counter data shows approximately 0.05–0.13% of page loads invoke the API (2022–2026). Firefox disabled the API on Android citing abuse concerns before removing it entirely from Firefox Desktop in v129 (Bug 1900037). WebKit's opposition cites device independence, unclear use cases, power consumption, annoyance/abuse potential, portability, and infeasibility of integration on Apple platforms ( WebKit standards position #267).