Closed
Bug 1198123
Opened 10 years ago
Closed 5 years ago
Specifying videoSource with getUserMedia isn't working
Categories
(Firefox :: Site Permissions, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1142123
People
(Reporter: melih, Unassigned)
Details
(Whiteboard: [getUserMedia])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36
Steps to reproduce:
Call getUserMedia, and establish a stream with a default videoSource
When prompted have the dialog "Always remember"
Close stream
Call getUserMedia, and try to set a new videoSource
Actual results:
Once remembered, only the default videoSource is used by a getUserMedia object in FF
Expected results:
The new videoSource should have been selected as the source for the getUserMedia object
Component: Untriaged → WebRTC: Audio/Video
Product: Firefox → Core
Comment 1•10 years ago
|
||
The bug is here: http://mxr.mozilla.org/mozilla-central/source/browser/modules/webrtcUI.jsm?rev=b6de7762bd17&mark=393-393#385
Persistent permissions should remember what device the user chose when they granted persistent permission, instead it always chooses the default device, as can be seen in the source above.
If the remembered device is not in the returned list (can happen if constraints are used, or the device is removed), then the default device should be used, otherwise the remembered device should be used. Relying on the name of the device seems sufficiently reliable to me.
Status: UNCONFIRMED → NEW
Component: WebRTC: Audio/Video → Device Permissions
Ever confirmed: true
Product: Core → Firefox
Version: 43 Branch → 40 Branch
Updated•10 years ago
|
Whiteboard: [getUserMedia]
| Reporter | ||
Comment 2•10 years ago
|
||
Thanks!
I just wanted to comment that this use case is still popping up fairly often at TokBox. Especially since we've released our Hardware Setup Component (https://github.com/opentok/opentok-hardware-setup.js), our customers (developers) are being exposed to a less than good experience in Firefox, while Chrome seems to work as expected.
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•