- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Sun, 19 May 2024 03:21:40 +0000
- To: public-device-apis-log@w3.org
It's still feels really wonky to have 3 permissions policies at play, which can be seen throughout the spec's: * for loop permission checks, and constantly checking if one or the other has changed. This means potentially having multiple UI options (3x!) which would be super confusing. If a user turns one off, it would break the other two in the case of "absolute" etc. * attempt to combine multiple permission into a single UI #183 This appears to be an issue because of #180. It appears that the only real reason to have the 3 policies is because of the Gyroscope, Accelerometer, and Magnetometer specs. If those are folded into this one, the three policies no longer make sense (as they also don't really make sense from a permissions UI perspective). Does chrome use a single "motion sensors" for this? If so, my point stands in that users can't ever set "I just want X, but not Y, and allow Z" so the three policies don't make a lot sense from a permission perspective.  What am I missing? -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/162#issuecomment-2119083248 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 19 May 2024 03:21:41 UTC