- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jun 2022 15:58:17 +0000
- To: public-device-apis-log@w3.org
Hmm, interesting. I don't have strong objections to the idea, although I don't know if this will confuse users depending on how the UI is constructed (e.g. a website asks for camera access although the camera indicator does not get turned on and no camera access seems to be happening). Let me try to summarize the new proposal: * ALS's _sensor permission names_ and _sensor feature names_ become "camera". * Calling `AmbientLightSensor.start()` would prompt for camera access (in whatever fashion the UA sees fit). If allowed by the user, this means that: * `navigator.mediaDevices.getUserMedia({ video: true })` would resolve without prompting * The UA would indicate somehow that the camera is being used (just like if camera access was being requested via `getUserMedia()`) * If a user revokes the camera permission, active ALS instances need to be stopped as well. I wonder if others would like to chime in before I work on a patch? @anssiko @kenchris @larsgk @marcoscaceres @willmorgan @engedy -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/ambient-light/issues/79#issuecomment-1171396882 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 June 2022 15:58:19 UTC