- From: Limin Zhu via GitHub <noreply@w3.org>
- Date: Wed, 25 Mar 2026 23:10:22 +0000
- To: public-css-archive@w3.org
@astearns good callout. To my knowledge links below are the most relevant information from webkit and gecko. I believe it comes down to - * `nav.vibrate` is too simple and doesn't provide means to be tactually expressive - intent-based new API address that directly * potential of annoyance/abuse, wasting power - addressed in the security section; notably UA may opt to apply throttling, and user may just navigate away from sites abusing haptics without lasting consequences * (this is not from the positions repo, but my view on what is different then and now) - landscape on haptics-capable devices has also been shifting. It goes from mostly "my phone (and some obscure device) can shake" to new Surface/Mac/other laptops are starting to ship with haptics trackpads and other accessories are coming online too. These points are separately addressed in the explainer, but not spelled out side-by-side to directly answer your question. Happy to tweak the explainer if you think this is useful. https://github.com/WebKit/standards-positions/issues/267#issuecomment-1767541211 https://github.com/mozilla/standards-positions/issues/907 -- GitHub Notification of comment by liminzhu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13728#issuecomment-4130412326 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 March 2026 23:10:23 UTC