Closed
Bug 1245475
Opened 9 years ago
Closed 9 years ago
WebRTC getUserMedia media device problems
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: ossavci, Unassigned)
Details
Attachments
(1 file)
23.54 KB,
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36
Steps to reproduce:
In webrtc, when I call getusermedia with constraints included device ids(canera,mic), then do renegotiations.
Actual results:
Whatever device id is firefox set selected device in its own popout window(attached in files). I cant change device usgin getusermedia with constraints,I have to change device from firefox popout.
Expected results:
Current devices have to be selected ids whic given in constraints.we have to no need to firefox popout.
Comment 1•9 years ago
|
||
Can you be more explicit on what you're doing, and what happens that you don't want/expect? Examples would be best, or code snippets, or an indication what calls you make with what arguments.
Renegotiation itself shouldn't pop a new GetUserMedia approval request; only a new GetUserMedia call would do that.
(In reply to Randell Jesup [:jesup] from comment #1)
> Can you be more explicit on what you're doing, and what happens that you
> don't want/expect? Examples would be best, or code snippets, or an
> indication what calls you make with what arguments.
>
> Renegotiation itself shouldn't pop a new GetUserMedia approval request; only
> a new GetUserMedia call would do that.
We made a new getusermedia call, we set device id that we want to use in constraints. we want set devices with getusermedia not a popout. but firefox show us a popout every getusermedia call.
Flags: needinfo?(ossavci)
Comment 4•9 years ago
|
||
Passing a device-id is not a substitute for user approval of access. Chrome hides this by making the default to approve permanently. We could perhaps allow access to a device you already have access to without re-asking without violating the spec (or violating the spirit) -- but on the other hand, you have no need/reason to do so - just reuse the existing stream.
I.e. don't call getUserMedia on renegotiation - that's in incorrect pattern, even if it happens to work ok in Chrome. Just use the current stream again to the new offer/answer.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•