Intent to Implement and Ship: RTCRtpReceiver.getParameters()

[Florent Castelli]

Contact emails

orp...@chromium.org

Spec

https://w3c.github.io/webrtc-pc/#dom-rtcrtpreceiver-getparameters

Summary

The getParameters() method returns the RTCRtpReceiver object's current parameters for how the track is decoded, which includes the codec and RTP header lists that have been negotiated for the call, some RTCP information and layer count in case of simulcast.

This is analog to RTCRtpSender.getParameters() with read-only information.

Motivation

Completeness of WebRTC 1.0 implementation, and more detailed view of the receiver's state.

Risks

Interoperability and Compatibility

Firefox: Positive to completing WebRTC 1.0

Edge: Positive to completing WebRTC 1.0

Safari: Shipped in current preview

Web developers: No signals

This API is part of the WebRTC 1.0 specification, all browsers have announced their intent to complete the implementation.

Ergonomics

This will be used with RTCPeerConnection and RTCRtpTransceiver.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux,

Chrome OS, Android, and Android WebView)?

Yes.

Link to entry on the Chrome Platform Status

https://www.chromestatus.com/features/5641443221700608

Requesting approval to ship?

Yes

[Philip Jägenstedt]

Is this fully testable using web-platform-tests? Given that it's already in Safari Technology Preview, are the results in https://wpt.fyi/results/webrtc?label=experimental?

Bit of the template I'm asking about pasted here:

Is this feature fully tested by web-platform-tests?

This section should be removed if “Requesting approval to ship?” is No.

Please link to the test suite. If any part of the feature is not tested by web-platform-tests, please include links to issues, e.g.:

• A web-platform-tests issue with the "infra" label explaining why a certain thing cannot be tested. (example)

• A spec issue for some change that would make it possible to test. (example)

• A Chromium issue to upstream some existing tests. (example)

An Intent to Ship requires either a web platform test suite or such issues to be filed explaining why such a test suite is currently impossible or in the progress of being upstreamed.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADRnnSUf7sumC4%2BRenogQADUBmU475oJ0N51fxgQd3jys%3D1MGQ%40mail.gmail.com.

[Florent Castelli]

I wonder how I forgot that piece of the template, sorry about that!

Is this feature fully tested by web-platform-tests?

Partially. I will add more tests for some specific scenarios not covered by this simple one.

[Philip Jägenstedt]

That is an impressive amount of comments for quite little test :) Thanks for taking care of improving that.

LGTM1

[Yoav Weiss]

LGTM2, considering the tests land with the implementation.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYet79KMkLoqQwU8KQYV%3DDXv1JKy835tXGB2Po7qApBsKA%40mail.gmail.com.

[Rick Byers]

LGTM3

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEjXRngScSXrFz%3DW%2B0H2bQvZaiQnHqZAwhv7tGkr4GEEDg%40mail.gmail.com.