FF142 RTCRtpSender.setParameters() encodings.codec param supported #27488
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FF142 adds support for the dictionary property
RTCRtpEncodingParameters.codecin https://bugzilla.mozilla.org/show_bug.cgi?id=1894137This is used when setting encodings in
RTCRtpSender.setParameters(parameter.encodings)andRTCPeerConnection.addTransceiver(sendencodings), and returned inRTCRtpSender/getParameters()(encodings.codec).This updates the
setParameters()- encodings - subfeature on the sender. ThegetParameters()andRTCPeerConnection.addTransceiverfeatures don't go down to the same level - my assumption is that you don't want to record this because it would likely always duplicate.The version values for chrome and safari were found by running https://wpt.live/webrtc/RTCRtpParameters-codec.html on browserstack.
Related docs work can be tracked in mdn/content#40477