Constraints in WebRTC not working yet. |
|||||||
Issue description
Google Chrome 55.0.2883.87 (Official Build) (64-bit)
Linux
1.
navigator.mediaDevices.getUserMedia({
video: {width: 1920, height: 1080}
});
Returns 640x480 stream, but it should return 1920x1080 in this case (supported by hardware).
2.
navigator.mediaDevices.getUserMedia({
video: {
advanced: [
{width: 1920, height: 1080},
{width: 800, height: 600},
{width: 640, height: 480}
]
}
});
Returns 640x480 stream even though the camera supports full HD.
3.
navigator.mediaDevices.getUserMedia({
video: {width: {ideal: 1920}, height: {ideal: 1080}}
});
Returns 640x480 stream, but it should return the closest to 1920x1080 supported by the hardware.
,
Dec 26 2016
,
Dec 26 2016
Alternatively, is there any way to open a camera with the highest resolution possible without blindly probing each resolution?
,
Jan 3 2017
Did any of these ever work in Chrome? If so, in which version? We're trying to make them all work for 57 per spec, but I don't see how they can hae worked before as intended.
,
Jan 4 2017
Hm, right. I was using the older constraints syntax with minWidth and minHeight. Sorry for the false alarm.
,
Jan 4 2017
,
Jan 11 2017
Thanks for the update! Since we want the newer constraints to work, I'm leaving it open, but reclassifying as P2 and targeting M58. These are good ideas for tests.
,
Mar 21 2017
@hta: Is there any progress with the new constraints?
,
Apr 5 2017
,
Apr 18 2017
Closing, since the examples in the summary now all work. Issue 543997 tracks the implementation of the whole API. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mtomasz@chromium.org
, Dec 26 2016Status: Assigned (was: Available)