- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Jun 2020 06:37:13 +0000
- To: public-webrtc-logs@w3.org
Step 6.3.4 of the getUserMedia algorithm is already marked with a fingerprint marker; this has been discussed before, and the decision at the time was to warn the implementors, not change the processing. The uncomfortable interaction if you swap the two is to get a permissions prompt, grant permission, and then get a "ha ha, you can't do this anyway" error message because you have no device that can satisfy the constraint. My suggestion: This can be revisited in @jan-ivar's proposed extension spec for a getUserMedia variant that mandates an in-chrome picker. In the meantime, I wouldn't want to change present behavior. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/697#issuecomment-645810850 using your GitHub account
Received on Thursday, 18 June 2020 06:37:15 UTC