Skip to content

Add waveform mapping table to Haptics explainer #1261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
neshgandhe wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add waveform mapping table to Haptics explainer #1261

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions Haptics/explainer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,15 @@ The parameters for `navigator.playHaptics`:

The API always returns `undefined`. No haptics is played if the last input device is not haptics-capable.

The table below illustrates example mappings of the pre-defined effects (Hover, Edge, Tick, Align) to representative platform-native feedback patterns across Windows, macOS, iOS, and Android. These mappings are illustrative examples only. User agents may choose different mappings, including synthesizing custom effects from lower-level primitives and parameters. The API standardizes the developer-facing intent, while the underlying realization remains platform-defined.

| Web Haptics | Windows | MacOS | iOS | Android |
|:-----------:|:-------:|:-----:|:---:|:-------:|
| Hover | hover | generic | light impact | gesture_threshold_deactivate |
| Edge | collide | generic | soft impact | long_press |
| Tick | step | generic | selection | segment_frequent_tick |
| Align | align | alignment | rigid impact | segment_tick |

## Sample code
```html
<html>
Expand Down