- From: Marcos Cáceres via GitHub <noreply@w3.org>
- Date: Sun, 12 Apr 2026 09:41:50 +0000
- To: public-device-apis-log@w3.org
@reillyeon @anssiko I've updated the implementation report based on the discussion. The main changes: **New: Historical implementation experience section** In response to @anssiko's feedback about the EFL WebKit port, the report now documents the full history: - Samsung's EFL port had Vibration API code from 2012, enabled via `ENABLE_VIBRATION` in `OptionsEfl.cmake` - The EFL port was removed from WebKit mainline in February 2017; the Vibration API code was removed in May 2017 ([Bug 171766](https://webkit.org/b/171766)) - The [ewebkit/webkit](https://github.com/ewebkit/webkit) fork retains the code but hasn't been updated since July 2017 - No WPT results exist for any EFL WebKit-based browser The Gecko (Firefox) lifecycle is also documented: supported from v16 (2012), disabled on Android from v79 (2020), removed on Desktop in v129 (August 2024). **New: Source code verification (April 2026)** All three engines verified directly in source, with repository links and specific file paths included so anyone can independently reproduce the findings: - **Blink** ([chromium/src](https://chromium.googlesource.com/chromium/src/)): `VibrationController` active in `vibration_controller.cc`, with user activation and cross-origin iframe guards - **Gecko** ([mozilla-central](https://searchfox.org/mozilla-central/source)): WebIDL and HAL code remain in tree, but gated on `dom.vibrator.enabled` which defaults to `false` in `StaticPrefList.yaml` on all platforms (including Android) since Firefox 129. No platform-specific override in `geckoview-prefs.yaml` or elsewhere. - **WebKit** ([WebKit/WebKit](https://github.com/WebKit/WebKit)): Zero vibration-related code in any IDL file, no `VibrationController`, no `ENABLE_VIBRATION` flag. Entirely absent. **Updated: Automated test results** Updated to match [current wpt.fyi results](https://wpt.fyi/results/vibration?label=experimental&label=master&aligned) (April 9, 2026). Firefox now shows FAIL (not STUB) since the API is no longer exposed on any platform. **Other fixes** - Chrome use counter data now cites the [actual source](https://chromestatus.com/metrics/feature/timeline/popularity/850) (bucket 850, 0.05–0.13% of page loads, 2022–2026) and links to [issue #33](https://github.com/w3c/vibration/issues/33) for the abuse investigation - Firefox Android citation corrected to reference [MDN compatibility data](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/vibrate#browser_compatibility) as primary source - WebKit concerns list updated to include "unclear use cases" -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/vibration/pull/55#issuecomment-4231229245 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 12 April 2026 09:41:51 UTC