Closed
Bug 1504892
Opened 6 years ago
Closed 6 years ago
Sender parameters are not reset after pc.removeTrack(sender)
Categories
(Core :: WebRTC: Signaling, enhancement, P3)
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox65 | --- | affected |
People
(Reporter: ibc, Unassigned)
Details
As described here: https://github.com/w3c/webrtc-pc/issues/2025 This is unclear in the spec. However IMHO it would make sense that, once `pc.removeTrack(transceiver.sender)` is called, if later we add a new track via `transceiver.sender.replaceTrack(newTrack)`, previous sender settings (such as simulcast/encodings) should be reset. However, this is not true in Firefox (previous sender parameters are kept).
Updated•6 years ago
|
Priority: -- → P3
Comment 1•6 years ago
|
||
We also need to think through whether send SSRC should change here.
Reporter | ||
Comment 2•6 years ago
|
||
May be there is nothing to fix: https://github.com/w3c/webrtc-pc/issues/2025#issuecomment-436593005
Comment 3•6 years ago
|
||
The spec seems clear about what removeTrack should do, and it doesn't involve resetting sender parameters, so I'm closing this issue.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•