New issue
Advanced search Search tips

Issue 909028 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 28
Cc:
vamshi.kommuri@chromium.org
guidou@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Can't remove constraints from video track using applyConstraints() with no argument

Reported by blahblah...@gmail.com, Nov 27 
UserAgent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3623.0 Safari/537.36

Steps to reproduce the problem:
1. Go to https://codepen.io/groupboard/pen/EOepLm
2. Give permission to use webcam
3. Click the "lo res" button
4. Click the "remove constraints" button.

What is the expected behavior?
Webcam image should change to low resolution (small image) when you click "lo res", and should go back to full size when you click "remove constraints".

What went wrong?
Stays stuck in low resolution. Works fine on Firefox. Spec says that passing no argument to applyConstraints should remove existing constraints, but this isn't happening on Chrome.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 72.0.3623.0  Channel: canary
OS Version: 10.0
Flash Version:

Comment 1 by vamshi.kommuri@chromium.org, Nov 28

Labels: Needs-Triage-M72

Comment 2 by vamshi.kommuri@chromium.org, Nov 28

Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Target-72 FoundIn-72 M-72 FoundIn-71 FoundIn-70 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Thanks for filing the issue!

Able to reproduce the issue on reported chrome version 72.0.3623.0 using Windows 10, Mac 10.14.1 and Ubuntu 17.10

Our Observations:
----------------
On Chrome version 60.0.3112.0 & 61.0.3133.0 - Couldn't see the video playing
On Chrome version 62.0.3202.94, clicking "lo res" button isn't changing image resolution.
From Chrome version 63.0.3239.132 the issue is seen, hence considering it as Non-Regression and marking it as Untriaged.

Comment 3 by guidou@chromium.org, Nov 28

Status: WontFix (was: Untriaged)
This is not a bug.
Removing constraints just removes restrictions on the settings the track can have.
It's perfectly valid to leave settings as they currently are.
It's also valid to change them to any other value (any settings are valid, including the current ones,  precisely because there are no constraints).
If you would prefer a resolution change you can pass the new resolution as ideal values  in applyConstraints(). In this case, if it's possible to change the resolution, Chrome will change it to whatever is closest to the ideal values.
You can also pass the new resolution as exact constraints, in which case, applyConstraints will force the new resolution if possible, but fail if it's not possible to change the track's resolution.

Closing this bug since this is WAI.
►

Sign in to add a comment