Re: [vibration] Integration with permissions API (#42)

@pes10k and the PING folks, thanks for your timely review!

We will be discussing this issue at TPAC F2F https://github.com/w3c/devicesensors-wg/issues/69 in context of overall wide review feedback dissemination. We'd love to pull you into that discussion, or visit an applicable PING session, to bring this issue to closure. For background, historical context relevant to your suggestion below, also included is questionnaire feedback for your consideration.

History first:

The group discussed Permissions API integration early on https://github.com/w3c/vibration/issues/10 and deferred the integration to a later version awaiting further implementation experience. Later, Chrome chose to implement user activation-gating https://github.com/w3c/vibration/issues/29 instead and that is what the latest editor's draft now reflects. IIRC that design decision was made informed by large-scale trials for both cross-origin and same-origin user activation-gating separately.

Then some feedback related to questionnaire stemming from this context. I hope this is helpful:

It appeared to me Web Platform Design Principles talks about user user activation and meaningful consent:
https://www.w3.org/TR/design-principles/#require-user-activation
https://www.w3.org/TR/design-principles/#consent

However, I believe there would be an opportunity also for the [Security and Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/) to provide further advice on how these two mechanisms should work together from a privacy perspective. When to choose one over another, or use both. Currently, the questionnaire ED talks about user activation in context of BFCache. A more general advice would make this consideration more visible to folks who conduct their self-reviews.

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/vibration/issues/42#issuecomment-2277380884 using your GitHub account


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

Received on Friday, 9 August 2024 07:59:07 UTC