webrtc-extensions
webrtc-extensions copied to clipboard
w3c
A repository for experimental additions to the WebRTC API
Please find "(FEATURE AT RISK) ISSUE 3" in https://w3c.github.io/webrtc-extensions/#rtcicecredentialtype-enum
Partially addresses: #217. This PR fixes some validation errors by replacing the shorthand links with data-cite, which suppresses the errors. This does not, however, fix the links to `RTCIceCandidatePair` in...
The addition of an [adaptivePtime member](https://w3c.github.io/webrtc-extensions/#dom-rtcrtpencodingparameters-adaptiveptime) to the `RTCRtpEncodingParameters` dictionary seems to have [reasonable test coverage](https://github.com/web-platform-tests/wpt/blob/master/webrtc-extensions/RTCRtpParameters-adaptivePtime.html), [one passing implementation](https://wpt.fyi/results/webrtc-extensions/RTCRtpParameters-adaptivePtime.html?label=experimental&label=master&aligned), and [implementation commitment from webkit](https://lists.webkit.org/pipermail/webkit-dev/2021-March/031763.html), so should be ready to migrate...
[Transferable data channels](https://w3c.github.io/webrtc-extensions/#rtcdatachannel-transferable) seems to have [reasonable test coverage](https://github.com/web-platform-tests/wpt/blob/master/webrtc-extensions/transfer-datachannel.html) and [one passing implementation](https://wpt.fyi/results/webrtc-extensions/transfer-datachannel.html?label=experimental&label=master&aligned). Relevant [Chromium bug report](https://issues.chromium.org/issues/40787712), [Firefox bug report](https://bugzilla.mozilla.org/show_bug.cgi?id=1209163) ; @alvestrand @jan-ivar can you comment whether these indicate something...
Ref: https://github.com/w3c/webrtc-pc/issues/2930. With the conversion of `RTCIceCandidatePair` from a dictionary to an interface, the XRef database contains some ambiguous duplicate definitions with differing types from multiple version of the "webrtc"...
[`RTCEncodingOptions.keyFrame`](https://w3c.github.io/webrtc-extensions/#dom-rtcencodingoptions-keyframe) (for keyframe generation request) has [reasonable test coverage](https://github.com/web-platform-tests/wpt/blob/master/webrtc/RTCRtpSender-setParameters-keyFrame.html) (although in the wrong directory at the moment), [one passing implementation](https://wpt.fyi/results/webrtc/RTCRtpSender-setParameters-keyFrame.html?label=master&label=experimental&aligned). @jan-ivar @youennf I could not find any signal of implementation...
The spec adds `captureTimestamp` and `senderCaptureTimeoffset` to [`RTCRtpContributingSource`](https://w3c.github.io/webrtc-extensions/#rtcrtpcontributingsource-extensions), yet the [corresponding test](https://github.com/web-platform-tests/wpt/blob/master/webrtc-extensions/RTCRtpSynchronizationSource-captureTimestamp.html) (and apparently the [implementation in Chromium](https://wpt.fyi/results/webrtc-extensions/RTCRtpSynchronizationSource-captureTimestamp.html?label=experimental&label=master&aligned)) has them in `RTCRtpSynchronizationSource`.
[`RTCRtpEncodingParameters.codec`](https://w3c.github.io/webrtc-extensions/#dom-rtcrtpencodingparameters-codec) seems to have [reasonable test coverage](https://github.com/web-platform-tests/wpt/blob/master/webrtc-extensions/RTCRtpParameters-codec.html), [one passing implementation](https://wpt.fyi/results/webrtc-extensions/RTCRtpParameters-codec.html?label=experimental&label=master&aligned), and implementation commitment from two other implementations ([Firefox](https://github.com/mozilla/standards-positions/issues/789), [webkit](https://github.com/WebKit/standards-positions/issues/179)) so should be ready to migrate to the main spec
The RTP header extension control feature seems to have [reasonable test coverage](https://github.com/web-platform-tests/wpt/blob/master/webrtc-extensions/RTCRtpTransceiver-headerExtensionControl.html), [with one implementation](https://wpt.fyi/results/webrtc-extensions/RTCRtpTransceiver-headerExtensionControl.html?label=experimental&label=master&aligned), and two additional implementation commitments ([Firefox](https://github.com/mozilla/standards-positions/issues/713#issuecomment-1519227603), [Webkit](https://github.com/WebKit/standards-positions/issues/100#issuecomment-1517509495)), so it seems to be ready to migrate...
### Background Following the incremental approach for improving ICE control capabilities, mechanisms are now defined to: - prevent the removal of a candidate pair by the ICE agent: #166 -...