Re: [mediacapture-main] Bug in spec: circular dependency for enumerateDevices() (#709)

> Let's get back to the initial request:
>
> > @hills to make sure I understand clearly your request: if permission to a device is granted, but opening that device fails for other reasons, then you argue that `enumerateDevices()̀` permission should be granted?
> 
> Are we good now in the fact that this has benefits but no identified drawbacks?

I'm having trouble parsing this, and other parts of the message. sorry. As it sounds as if you are asking if I agree with my own (older) point which, of course, I do. But since then we discussed your privacy concerns, and incorporated them, so I think it is helpful not to go backwards.

This is the current concern: ([full context](https://github.com/w3c/mediacapture-main/issues/709#issuecomment-691139860)). Can this be implemented?

>  * Access to both APIs, enumerateDevices() and getUserMedia() based on the permission check _with no extra conditions_
>  * Activate the capture indicator _on any reveal of information_ including:   
>       * device opened successfully
>       * device failed to open
>       * reveal of any deviceID (enumerateDevices)

This outlines an, overall, much better fix to this ticket than that which was merged; and better direction in general. It has benefits, and no identifiable drawbacks, as you say. 

You say the capture indicator ("camera" icon, typically) falls outside of the spec, that is even better. The capture indicator can be oriented to achieve the desired privacy goals; the spec focuses on maintaining a clear API without quirks (it also happens to be in line with the historical API so does not break existing code)

-- 
GitHub Notification of comment by hills
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/709#issuecomment-697850765 using your GitHub account


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

Received on Wednesday, 23 September 2020 18:32:37 UTC