Currently, Chrome supports the new spec syntax for constraints, but it does not fully implement the SelectSettings algorithm as specified in https://w3c.github.io/mediacapture-main/#dom-mediadevices-getusermedia.
This bug tracks the development of this feature, which is required for fully spec-compliant getUsermedia() and applyConstraints().
The patch in #13 will still fail the getUserMedia request from appr.tc and other webrtc samples on Android. (the one in #11 used to fail on all platforms)
You can refer the issue691559 for the error. Same in ToT Chromium, as #450095 in my test.
braveyao: can you check if non-Android platforms still break?
#13 and #11 are identical, except for a fix to a Webview test that depended on nonstandard behavior.
The fix for issue 691559 fixed the Android problems. Maybe other platforms had the same issue?
No. The patch in #11 did cause gUM problem on all platforms. But the patch #450026 in #13 works fine on non-Android platforms. The ToT works on all platforms now.
Maybe it's due to the different failure reason. On Android it's DeviceNotFound. On other platforms(as I can remember) it's about track creation failure...
You may need to double check :)
Comment 1 by guidou@chromium.org
, Dec 1 2016