- From: Limin Zhu via GitHub <noreply@w3.org>
- Date: Mon, 10 Aug 2026 20:36:22 +0000
- To: public-css-archive@w3.org
It’s a very useful discussion of the idea! Is it right to think of the tradeoff between the nested at-rule and the event-trigger model as: - The nested `@haptic` model is simpler, but: - it is less directly tied to the input and; - it may require a style update before the haptic can be actuated, which could be slow for interactions like snapping. - The event-trigger model makes the cause/effect relationship explicit and can be actuated closer to the input, but: - its syntax is somewhat more verbose; - it depends on the Animation Triggers model reaching a sufficiently stable shape; - it requires more specification work around haptic actions, eligible event sources, and possibly anonymous trigger syntax; - in simple (and possibly common) cases, an event trigger can feel like unnecessary aliasing, so an anonymous trigger syntax or shorthand may be useful. -- GitHub Notification of comment by liminzhu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13728#issuecomment-5245674358 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 August 2026 20:36:22 UTC