- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jun 2022 16:11:53 +0000
- To: public-device-apis-log@w3.org
rakuco has just created a new issue for https://github.com/w3c/ambient-light: == Add camera permission requirement to spec? == See https://www.w3.org/2021/10/29-dap-minutes.html#t07: > RESOLUTION: Add camera permission requirement to ALS spec to help enable shipment of the API If I've understood it correctly, the idea would be to add text to the spec that mandates that permission for accessing ALS would be granted only if access to ALS as well as camera is allowed (in a similar fashion to `getUserMedia()` and the microphone/camera permissions, for example). I'd like to make sure that this is indeed the idea, especially in light of https://github.com/w3c/ambient-light/issues/64#issuecomment-954444294 (_This will require continuous monitoring of the ALS and not make sense to bundle with a camera API (including permissions)_). I'm also wondering if this makes sense as a normative requirement or as an implementation detail. The DAS F2F discussion mentioned Chrome's position: > we'd be willing to enable the ALS API for websites that use camera already > we could consider ALS augmenting the camera in this case, isn't it up to the UA to do one of the following: - Reject calls to `AmbientLightSensor.start()` if access to the camera has not been granted before - Show a custom prompt for ALS that would cause access to camera and ALS to be granted together - Automatically grant access to ALS if access to the camera has already been granted - Something else entirely Please view or discuss this issue at https://github.com/w3c/ambient-light/issues/79 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 June 2022 16:11:54 UTC