- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Oct 2020 13:23:19 +0000
- To: public-webrtc-logs@w3.org
> Sites are going to do things like:
>
> ```js
> await navigator.mediaDevices.getUserMedia({video: {deviceId: deviceFromLastVisitId, height: 1080}});
> ```
>
> ...and expect comparable results across browsers (same device if available, or comparable 1080p cam if not).
Well, that expectation would be misplaced. Currently there is zero consistency with regard to browsers and video device selection: Firefox and Chromium proffer different devices as default https://github.com/w3c/mediacapture-main/issues/727.
Chromium does not support capture of monitor devices and uses the label `"audiooutput"` when in fact that is the exact same device as the microphone, and neither this specification nor Audio Output Devices API actually define capture of headphones or speakers.
"SHOULD" is still not strong enough for these billigerent implementers. Am skeptical that "MUST" is even strong enough language, yet with "MUST" there is no ambiguity with regard to intent of the authors.
--
GitHub Notification of comment by guest271314
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/735#issuecomment-704932695 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 October 2020 13:23:21 UTC