[vibration] Misc non-privacy concerns with the API (#43)

pes10k has just created a new issue for https://github.com/w3c/vibration:

== Misc non-privacy concerns with the API ==
This issue is filed as part of the PING review requested here https://github.com/w3cping/privacy-request/issues/138

The following are a list of non-privacy related concerns that were identified during the PING review.

- the API describes async behavior (the vibration happens at some point after the `vibrate()` all, but uses a sync API.  I suggest making this an async API instead
- the text seems contradictory. For example, in the "Validate and Normalize" subsection, the first note says implementors could respond to a too-long vibration request in a bunch of different ways (reject it, truncate it, split it into multiple vibrations). However item 2 in that subsection says that implementors must truncate. This is confusing
- the large amount of intentionally un-standardized behavior is concerning in general (e.g., what to do with a too-long vibrate request, whether a given request should trigger a vibration at all, if there is a cap on vibrations, what makes a page trusted and so can vibrate even if the page isn't visible, and even ultimately when `vibrate()` returns `true` or `false`)

Please view or discuss this issue at https://github.com/w3c/vibration/issues/43 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 18 July 2024 17:29:17 UTC