- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Sep 2020 16:17:22 +0000
- To: public-webrtc-logs@w3.org
> Currently, some browsers will not produce a 160x160
Which browsers?
Chromium 87 and Nightly 83 both produce a 160x160 video.
```
navigator.mediaDevices.getUserMedia({video: true})
.then(async stream => {
const video = document.createElement('video');
document.body.appendChild(video);
video.autoplay = true;
video.srcObject = stream;
const recorder = new MediaRecorder(stream);
recorder.ondataavailable = ({data}) => console.log(URL.createObjectURL(data));
recorder.start();
setTimeout(async _ => {
await stream.getVideoTracks()[0].applyConstraints({ width : 160, height : 160 });
setTimeout(_ => recorder.stop(), 5000);
}, 5000);
});
```
[chromium_87_apply_constraints_width_height.webm.zip](https://github.com/w3c/mediacapture-main/files/5277571/chromium_87_apply_constraints_width_height.webm.zip)
[nightly_83_apply_constraints_width_height.webm.zip](https://github.com/w3c/mediacapture-main/files/5277574/nightly_83_apply_constraints_width_height.webm.zip)
> It would be nice to get interoperability for width and height constraints amongst browsers.
> The incompatibility between Chrome and Firefox modes
While testing the claims made found that when two (2) different USB cameras are connected to the machine Chromium and Firefox select different devices as the default camera. That is definitely an interoperabilty and incompatibility issue.
--
GitHub Notification of comment by guest271314
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/723#issuecomment-698445978 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 September 2020 16:17:24 UTC