- From: hills via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Sep 2020 19:13:53 +0000
- To: public-webrtc-logs@w3.org
"The change" which I refer is the subject of this bug report; the very first paragraphs. Pull request #717 is inconsequential as it merely complicates the state of affairs. For the avoidance of doubt, here's the same summary with context: ---- This new condition in enumerateDevices (summarised in commit [c15a432](https://github.com/w3c/mediacapture-main/commit/c15a432b353efda4d86c6029976d79c2bcdcc69c), March 2020): > if the browsing context did not capture (i.e. getUserMedia() was not called or never resolved successfully), the MediaDeviceInfo object will contain a valid value for kind but empty strings for deviceId, Previously this read: > if no such access has been granted [...] The upsides of the change: * a perceived "privacy enhancement" around capture indicators. But our discussion shows this change cannot be realised in practice. The downsides: * change in API behaviour affects existing code in the wild * the new behaviour is unusual and not straightforward (I am not the only person already asking for clarification) * the new behaviour is not efficient (examples given require multiple device opens to workaround new behaviour) This is a robust case for the previous behaviour. -- GitHub Notification of comment by hills Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/709#issuecomment-687331845 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 September 2020 19:13:54 UTC