Re: [dap-charter] DASWG: Drop Ambient light sensor API for privacy and lack of implementer support (#100)

Thanks for asking @samuelweiler 👍 

Basically, the inability to determine the ambient brightness has a negative impact on user experience of our service in some cases when used within a browser. I wrote a detailed description of our use case here: https://github.com/w3c/ambient-light/issues/13#issuecomment-496935850

The only other way to determine the ambient brightness is to read the values from the camera settings after auto exposure has taken place (which is the technique we use in our native SDKs). However, this is currently not possible within a browser as being discussed here: https://github.com/w3c/mediacapture-image/issues/209

Considering all sensors, our view is that the ALS is most similar to the motion sensors (although arguably provides a lot less information, especially with the new mitigations in place) so should follow the same permissions model which is to be enabled by default (to prevent dialog box fatigue) but be easily disabled for those who want to.

I'm very happy to provide more details on anything if helpful. Thanks for your consideration.

-- 
GitHub Notification of comment by Joe-Palmer
Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/100#issuecomment-682126855 using your GitHub account


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

Received on Thursday, 27 August 2020 18:49:09 UTC