Open
Bug 1041769
Opened 10 years ago
Updated 2 years ago
Add test cases for screen sharing in a separate peer connection
Categories
(Core :: WebRTC, defect, P4)
Core
WebRTC
Tracking
()
NEW
backlog | webrtc/webaudio+ |
People
(Reporter: drno, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webrtc-mochitest])
Add a second peer connection with screen sharing to an existing call with a peer connection (audio only, video only, audio and video). Note: we do not have any test case yet with more then one peer connection.
Comment 1•9 years ago
|
||
Nils -- Did these tests get added on a different bug, or is this bug still valid?
Rank: 35
Flags: needinfo?(drno)
Priority: -- → P3
Reporter | ||
Comment 2•9 years ago
|
||
No they did not. Neither do we seem to have a mochitest for negotiating initial screen/window sharing together with some A/V (note: multistream). No do we seem to have a mochitest which adds a screen/window share to an existing PeerConnection (note: re-negotiation). And also we still don't have any mochitests which deal with multiple PeerConnections. Although the question is if multiple PeerConnections would become legacy at some point after all services have switched to multistream.
Flags: needinfo?(drno)
Reporter | ||
Updated•9 years ago
|
Whiteboard: [webrtc-mochitest]
Updated•9 years ago
|
backlog: --- → webRTC+
Comment 3•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•