Naked values in constraints are dependent on context for interpretation
Reported by
hta@webrtc.org,
Dec 13 2016
|
|||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36
Steps to reproduce the problem:
Pass {advanced: [{facingMode: "front"}]} as a camera constraint. Look at what's produced at the Web* layer.
What is the expected behavior?
It should return "front" as an exact constraint.
What went wrong?
It ends up in "ideal", just like "basic".
Did this work before? No
Does this work in other browsers? N/A
Chrome version: 54.0.2840.100 Channel: n/a
OS Version:
Flash Version: Shockwave Flash 23.0 r0
Spec: https://w3c.github.io/mediacapture-main/#constrainable-interface
,
Dec 14 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c43f9fc3ae40f693a01718627f75fe05d0fb9a80 commit c43f9fc3ae40f693a01718627f75fe05d0fb9a80 Author: hta <hta@chromium.org> Date: Wed Dec 14 12:04:18 2016 Make naked values in constraint behave right in "advanced" In "advanced" constraints, naked values are to be treated as "exact". In "basic" constraints, they should be treated as "ideal". BUG= 673734 Review-Url: https://codereview.chromium.org/2569233002 Cr-Commit-Position: refs/heads/master@{#438484} [modify] https://crrev.com/c43f9fc3ae40f693a01718627f75fe05d0fb9a80/third_party/WebKit/LayoutTests/fast/mediastream/MediaStreamTrack-getConstraints.html [modify] https://crrev.com/c43f9fc3ae40f693a01718627f75fe05d0fb9a80/third_party/WebKit/Source/modules/mediastream/MediaConstraintsImpl.cpp [modify] https://crrev.com/c43f9fc3ae40f693a01718627f75fe05d0fb9a80/third_party/WebKit/Source/modules/mediastream/MediaConstraintsTest.cpp
,
Jan 11 2017
,
Jan 12 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by hta@chromium.org
, Dec 13 2016Owner: hta@chromium.org
Status: Started (was: Unconfirmed)