Open
Bug 1130185
Opened 9 years ago
Updated 2 years ago
We need some renegotiation mochitests that test adding a track to a pre-existing stream
Categories
(Core :: WebRTC: Signaling, defect, P3)
Core
WebRTC: Signaling
Tracking
()
NEW
backlog | tech-debt |
People
(Reporter: bwc, Unassigned)
References
Details
Right now, our mochitest suite is not equipped to cause tracks to be added to a previously negotiated media stream, nor does it listen for or check the addtrack events that would result.
Reporter | ||
Updated•9 years ago
|
backlog: --- → tech-debt
Rank: 30
Priority: -- → P3
Reporter | ||
Comment 2•8 years ago
|
||
I think it is still something we need to do.
Flags: needinfo?(docfaraday)
Comment 3•8 years ago
|
||
Right - this was P3 30, and marked tech-debt. The (poorly asked) question was meant to be "do we need to reassess how soon we need this?" (Given all the other track-related changes that have landed)
Reporter | ||
Comment 4•8 years ago
|
||
I could see this being a P2.
Updated•8 years ago
|
Rank: 30 → 25
Priority: P3 → P2
Comment 5•8 years ago
|
||
I added a test in bug 1246310 but we could do with some more.
Reporter | ||
Comment 6•8 years ago
|
||
It looks like this is going to have some overlap with bug 998546, because both require the mochitest code to pay attention to ontrack.
See Also: → 998546
Comment 7•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•