- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jun 2024 06:37:35 +0000
- To: public-device-apis-log@w3.org
This one is fun too: https://wincard.thecashmint.com/?vibrate=123 It tries to vibrate through a URL parameter when everything load😹... and get blocked:  Anyway, I hope this report helps clarify the state of the Vibration API on the open web: - No actual interoperability, as demonstrated by the report. - Two out of three engines have pulled support over concerns of misuse. - Evidence of abuse and misuse at scale. - Chrome has implemented its own abuse mitigation due to high levels of misuse. - The specification lacks maintenance, with deficiencies filed as issues since 2016. It's truly astounding that this API remains with a "W3C Recommendation" status, given the above - and it's both shocking and disheartening that, despite overwhelming evidence, some here are seriously advocating that it should retain the "Recommendation" status. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/vibration/issues/33#issuecomment-2159909652 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 June 2024 06:37:36 UTC