Closed
Bug 1436302
Opened 7 years ago
Closed 7 years ago
The camera capture stops if you try to change the default camera during a call
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(firefox60 affected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox60 | --- | affected |
People
(Reporter: Ovidiu, Unassigned)
References
(Depends on 1 open bug)
Details
Affected versions]:
Tested on Nightly 60.0a1(2018-02-06)
[Affected platforms]:
Tested on Mac OS X 10.12, Ubuntu 16.04
[Steps to reproduce]:
Prerequisites:
1. Make sure you have 2 cameras connected to your system.
STR:
1. Open Firefox and start a Facebook call.
2. Change the default camera.
[Expected result]:
The camera starts to capture.
[Actual result]:
The camera capture freezes and the changing of cameras is not done.
NOTE: I tested on Facebook, jitsi, appear.in.
Reporter | ||
Comment 1•7 years ago
|
||
The same result on Windows.
Updated•7 years ago
|
Rank: 15
Priority: -- → P2
Reporter | ||
Comment 2•7 years ago
|
||
Updates: With appear.in this issue is not reproducible because the site has a different way of handling the changing of cameras when you want to change the default camera the call is refresh and the permission drop down is displayed.
Updated•7 years ago
|
Assignee: nobody → apehrson
Comment 3•7 years ago
|
||
I tested with meet.jit.si and I think this comes down to doing
`navigator.mediaDevices.getUserMedia({video: {deviceId: chosenId}})` instead of
`navigator.mediaDevices.getUserMedia({video: {deviceId: {exact: chosenId}}})`.
We behave correctly for the latter case.
For the former, without `exact` we see the request as flexible in terms of which device to choose, and since capture of another device is already live, that weighs heavier and we allow that.
jib, can you comment on the spec aspect of this? Is this something we should reasonably fix, or should we focus on outreach?
Flags: needinfo?(jib)
Comment 4•7 years ago
|
||
This is a legitimate bug. I've opened bug 1443294 to cover it.
But the websites are wrong too, so we should reach out to them. They really should be using exact constraints:
mediaDevices.getUserMedia({video: {deviceId: {exact: chosenId}}})
...to avoid substitutions in their selections. This prevents user-override in the Firefox permission prompt. Less confusing UI.
And it avoids bug 1443294.
Component: WebRTC: Audio/Video → Desktop
Depends on: 1443294
Flags: needinfo?(jib)
Product: Core → Tech Evangelism
Version: 60 Branch → Firefox 53
Updated•7 years ago
|
Assignee: apehrson → nobody
Comment 5•7 years ago
|
||
Unless we have bugs for every site using that pattern... this bug is a WONTFIX. Fixing 1443294 seems like a better option (and one we can control).
If someone disagrees, please reopen and let's file individual bugs with URLs, thanks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•6 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•