Re: [vibration] Add implementation report (#55)

Thanks for the context, @anssiko.

To be clear about what the claim in question is:

> "The EFL WebKit port includes an implementation of the Vibration API."

A few points about the evidence:

**The source linked doesn't support the claim.** The trac.webkit.org/wiki/EFLWebKit page (last modified October 2015) makes no mention of Vibration API support. It describes the port's features generally but does not document Vibration as an enabled capability.

**The EFL port was removed from WebKit in February 2017.** Commits from 2017-02-16 and 2017-02-17 removed EFL-specific files from Source, WebKit2, and Tools. The port was already gone three months before the Vibration API removal.

**Bug 171766 is the authoritative primary source.** Filed 2017-05-06 by WebKit engineers, RESOLVED FIXED 2017-05-11, the rationale states verbatim: "Not enabled by any ports / Tests are skipped by all ports / Unmaintained code." The phrase "any ports" is inclusive — it covers EFL and every other port that existed at or before that point.

**Code landing vs. shipped implementation.** Even setting the above aside, the standard for this implementation report is whether the API was shipped and interoperable — not whether code was landed. The 2013 blog post ("Samsung's Kihong Kwon landed initial support") describes a code landing. Bug 171766 explicitly records the outcome: that code was never enabled by any port before being removed.

The implementation report's conclusion — single-engine (Chromium/Blink only) — is grounded in the primary sources above. If there is verifiable evidence that the Vibration API was enabled and passing tests in a shipped EFL product, please share the specific source. Personal recollection is a useful starting point but not sufficient for an implementation report that will inform W3C REC advancement criteria.


-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/vibration/pull/55#issuecomment-4173033183 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 1 April 2026 21:20:08 UTC