*Contact emails*
[email protected], [email protected]

*Explainer*
https://github.com/WICG/web-haptics

*Specification*
*No information provided*

*Summary*
Provides semantic haptic feedback for web interactions through CSS and 
JavaScript, allowing web apps to trigger platform-appropriate tactile 
effects such as hints, ticks, alignment confirmations, and boundary 
signals. Developers can express haptic intent instead of creating 
device-specific vibration patterns, enabling consistent tactile feedback 
across desktop and mobile platforms. The API supports both declarative 
CSS-based haptics for common UI state changes and imperative JavaScript 
control for interaction logic that requires runtime decisions, while 
respecting platform settings.

*Blink component*
Blink>Vibration 
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EVibration%22>

*Web Feature ID*
Missing feature

*Motivation*
Web developers currently have limited options for providing tactile 
feedback. The existing `navigator.vibrate() 
<https://developer.mozilla.org/en-US/docs/Web/API/Navigator/vibrate>` API 
is mobile-centric, lacks broad platform support, and requires developers to 
define low-level vibration patterns rather than expressing the intended 
feedback effect. Developers also have no declarative way to associate 
haptics with common UI interactions such as scroll snapping, button 
presses, panel transitions, or form validation without introducing 
JavaScript. The Web Haptics API provides a semantic, cross-platform model 
for haptic feedback. Developers can request platform-appropriate effects 
such as hints, ticks, alignment confirmations, and boundary signals, while 
user agents map those effects to the capabilities of the underlying 
operating system and hardware. The API includes both a JavaScript interface 
for dynamic interactions and a CSS-based mechanism that enables low-latency 
haptic feedback directly from UI state changes. This approach aligns haptic 
authoring with developer intent, respects platform settings, and reduces 
the need for device-specific vibration tuning.

*Initial public proposal*
WICG: Web Haptics API · Issue #262 · WICG/proposals 
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWICG%2Fproposals%2Fissues%2F262&data=05%7C02%7Cakyereboah%40microsoft.com%7C836af4eaaea54badcba108dedc50a54c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C639190436164112499%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=aoW2ZpYWXObnpcFFgca8LeDJmSj66bFaAK5x5DlL1CQ%3D&reserved=0>
CSSWG: Proposal: Declarative Web Haptics · Issue #13728 · w3c/csswg-drafts 
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Fissues%2F13728&data=05%7C02%7Cakyereboah%40microsoft.com%7C836af4eaaea54badcba108dedc50a54c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C639190436164123659%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=uohfJYTn9zhP5094HigpU1sQ1Y4MwzzehcVSG8qptXQ%3D&reserved=0>

*Tracking bug*
https://issues.chromium.org/issues/531787872

*Estimated milestones*

No milestones specified


*Link to entry on the Chrome Platform Status*
https://chromestatus.com/feature/5167864517623808?gate=5082478395129856

This intent message was generated by Chrome Platform Status 
<https://chromestatus.com/>.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/62ad388e-e8bc-4665-90fc-41af04adc961n%40chromium.org.

Reply via email to