Re: [ambient-light] Add camera permission requirement to spec? (#79)

> Ideally we could bundle it up with all the other cameras in the existing "camera" permission but as @rakuco pointed out, the Media Capture spec supports granting permission to individual cameras. I'm not sure how to resolve that.

In addition to that, I feel it's hard to use the "camera" permission in a way that does not either break or weaken the requirements of the Media Capture spec. As mentioned in https://github.com/w3c/ambient-light/issues/79#issuecomment-1180571834 I think we'd need to think of the enumerability of ambient light sensors, how they integrate into Media Capture's [Privacy Indicator Requirements](https://w3c.github.io/mediacapture-main/#privacy-indicator-requirements), the [`DevicePermissionDescriptor` and `CameraDevicePermissionDescriptor` dictionaries](https://w3c.github.io/mediacapture-main/#permissions-integration) and the internal slots used in the spec, for example.

If we were _not_ to use the "camera" permission, I think we'd have to deal with two problems:
1. Possibly showing multiple permission prompts to users coming from multiple APIs/specs.
1. Communicating what permission is required in a way that users can understand.

Aren't they both user agent concerns more than spec ones though? A UA could choose not to show a prompt, or delay showing it to bundle it with others based on whatever heuristics or data it chooses (1), and a UA could also choose to implement some UI for ALS requests similar to what it shows for media capture (2).

Based on the concerns and possible issues with using the "camera" permission, maybe abandoning this idea would lead to less work and confusion?

-- 
GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/ambient-light/issues/79#issuecomment-1199660679 using your GitHub account


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

Received on Friday, 29 July 2022 16:19:55 UTC