Firefox currently supports an old version of RTCRtpSender.getParameters() 
and RTCRtpSender.setParameters(), which has changed significantly in more 
recent versions of the webrtc-pc spec. The most important change is the 
introduction of a transaction model, wherein setParameters() can only be called 
with the results of the most recent getParameters() call, with the desired 
modifications.

   This change is not backward compatible with the present implementation, 
because the webrtc-pc spec has changed in a non-backward-compatible way. It is 
likely that existing code using RTCRtpSender.setParameters() will need to be 
updated to work with the new version of this API.

Bugs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1534687
https://bugzilla.mozilla.org/show_bug.cgi?id=1401592
https://bugzilla.mozilla.org/show_bug.cgi?id=1531458

Standard: https://w3c.github.io/webrtc-pc/

Testing:
testing/web-platform/tests/webrtc/RTCRtpParameters-*
testing/web-platform/tests/webrtc/RTCRtpSender-setParameters.html
testing/web-platform/tests/webrtc/protocol/video-codecs.https.html
dom/media/tests/mochitest/test_peerConnection_setParameters.html

Cross-browser support: Chrome (and Edge) supports the more recent version of 
this API. Safari appears to have partial support for this API, but does not 
pass the relevant web-platform-tests.

Platform coverage: All

Target release: 78

Preferences behind which this will be implemented: None
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to