anssiko
commented
3 weeks ago @matatk and APA WG, thank you for your re-review. The context and rationale for the recent change in this RFC 2119 term is in https://github.com/w3c/vibration/pull/47#pullrequestreview-2393739221
The group's plan is to imminently publish a new CRS that matches current implementations and to continue evolve the specification with special consideration for issues -- including this one -- that suggest changes to existing implementations and thus may impact web compatibility.
The group is aware of an early experimental implementation in Firefox that showed a UI to the user to allow disable the API. We want to gather more implementation experience on this. The past design discussions around this feature are documented in 2.11 of https://github.com/w3c/vibration/issues/36 to inform the work.
The group would like to explicitly confirm with you that APA WG is supportive of this approach so that we can proceed with the CRS publication. Thank you!
matatk
The Security and privacy considerations section states:
APA WG previously reviewed this API and made a comment that users SHOULD be able to disable use of the API. We've reviewed the latest version, and feel that things have changed such that this requirement ought to be a (RFC 2119) MUST now. Here are the key reasons:
More apps could be using vibration as a means to send signals to the user via notifications, as well as the OS. There are also many frequent sources of notifications these days. There is scope for the user to be confused as to which app (or part of the OS) is sending the notification.
Some users may find the haptic feedback too intense. Notifications could be jarring for them, and games (where the vibrations may happen very often) could be difficult for them to interact with, due to the frequent haptic feedback.