Closed
Bug 1396918
Opened 7 years ago
Closed 2 years ago
Implement |sendEncodings| in RTCRtpTransceiverInit (for addTransceiver)
Categories
(Core :: WebRTC: Signaling, enhancement, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1401592
People
(Reporter: bwc, Unassigned)
References
(Blocks 1 open bug)
Details
This is likely to depend on other updates to set/getParameters, since we're pretty far from spec right now.
|
||
Updated•7 years ago
|
Rank: 25
Priority: -- → P2
|
||
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
|
Reporter | |
Updated•5 years ago
|
Summary: Implement |sendEncodings| in RTCRtpTransceiverInit → Implement |sendEncodings| in RTCRtpTransceiverInit (for addTransceiver)
|
||
Comment 2•5 years ago
|
||
Wit Chrome M74 adhering to the spec, it would be really sad that Firefox comes late to this. Currently Firefox allows changing the number of encodings via rtpSender.setParameters(). The spec clearly states that the number of encodings can just be set in the sendEncodings field of the RTCRtpTransceiverInit (which Firefox ignores).
|
|
Reporter | |
Comment 3•5 years ago
|
||
Another wpt that fails because of this bug landed in bug 1532123.
See Also: → 1532123
|
||
Comment 4•3 years ago
|
||
This is low-hanging fruit that causes unnecessary web compat issues with simulcast. Up-prioritizing.
Priority: P3 → P2
|
|
||
Comment 5•2 years ago
|
||
For folks coming here looking for a workaround, this is shimmed in adapter.js.
|
|
Reporter | |
Comment 6•2 years ago
|
||
Bug 1401592 will handle this.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•