- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Tue, 21 Apr 2026 14:00:27 +0000
- To: public-css-archive@w3.org
In your [alternatives considered](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Haptics/explainer.md#alternatives-considered), you list the animation trigger alternative as
```css
@haptic bounce-land { effect: align; intensity: 0.8; }
button:active { haptic-name: bounce-land; }
```
Suggesting that it is required even for the UA-defined haptics names. This was not the intention of my suggestion in https://github.com/w3c/csswg-drafts/issues/13728#issuecomment-4164100971. I was thinking that like view transition animations, there could be ua defined haptic names for which you wouldn't need to refer to an @-rule, but if you want to define new haptics we could define a syntax with an @-rule to create them similar to creating custom keyframe animations.
I.e. for built-in haptic names, it would still just be a single line:
```css
button:active { haptic: align 0.8; }
```
But in the future we could allow declaring custom names.
--
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13728#issuecomment-4289129546 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 April 2026 14:00:28 UTC