Closed
Bug 1017990
Opened 10 years ago
Closed 9 years ago
ability to change source of media stream without requiring renegotiation
Categories
(Core :: WebRTC: Audio/Video, defect, P1)
Core
WebRTC: Audio/Video
Tracking
()
RESOLVED
FIXED
backlog | webrtc/webaudio+ |
People
(Reporter: shell, Assigned: jesup)
References
(Blocks 1 open bug)
Details
(Whiteboard: breakdown [investigation])
scenario: after someone calls, use wants to plug in a headset rather than speakers. Needs UI.
More complex scenario than checking for new devices when door hanger is up scenario: bug 827146.
Comment 1•10 years ago
|
||
The WebRTC and gUM specifications do not currently support this
use case.
Assignee | ||
Comment 2•10 years ago
|
||
(In reply to Eric Rescorla (:ekr) from comment #1)
> The WebRTC and gUM specifications do not currently support this
> use case.
Right. And as discussed at the WG Interim (and elsewhere), we need something like this less cumbersome and more functional than using a <video> element as a track-switch (and even that requires non-spec functions - mozCaptureStream). So the general idea would be to propose a design and create a moz* implementation of it.
Comment 3•10 years ago
|
||
I think we need this for switching cameras.
Target Milestone: mozilla34 → mozilla33
Comment 4•10 years ago
|
||
Randell -- I think this needs some bug breakdown. Can you get the bugs into bugzilla for switching cameras without renegotiation based on our last meeting?
Assignee: nobody → rjesup
Priority: -- → P1
Whiteboard: p=? → p=1, breakdown
Reporter | ||
Updated•10 years ago
|
Whiteboard: p=1, breakdown → p=1, breakdown [investigation]
Updated•10 years ago
|
Target Milestone: mozilla33 → mozilla34
Comment 5•10 years ago
|
||
Breakdown complete
Comment 6•10 years ago
|
||
Any more to do here or can this be closed as well?
Reporter | ||
Updated•9 years ago
|
backlog: --- → webRTC+
Rank: 15
Whiteboard: p=1, breakdown [investigation] → breakdown [investigation]
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•