- From: Daniel Burnett via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 May 2017 14:11:27 +0000
- To: public-webrtc-logs@w3.org
The following commits were just pushed by burnburn to https://github.com/w3c/webrtc-pc: * Specify which encoding parameters can be set through sendEncodings. Fixes #1073. All read-write parameters and `rid` can be set, but the rest are ignored, as decided in the April virtual interim. Also added some detail to `getParameters` description, explaining that it should return the previously provided `sendEncodings` even if `setRemoteDescription` hasn't been called yet. I'm not yet addressing the simulcast error point that arose in the discussion of the issue. We can address that after we finish fleshing out how simulcast errors will be handled in the first place. by Taylor Brandstetter https://github.com/w3c/webrtc-pc/commit/9cadefe1761cd8d05f2e01ed210648bfb53f71a1 * Adding more detail about `getParameters` for both `RTCRtpSender` and `RTCRtpReceiver`. by Taylor Brandstetter https://github.com/w3c/webrtc-pc/commit/8804740528752c72c5b30210d931767a5a65cac6 * Throw an error if a read-only parameter is passed into addTransceiver. by Taylor Brandstetter https://github.com/w3c/webrtc-pc/commit/22b2ae1dfba75ebedf95b5c2456bc3509b1f7360 * Describe how RTCRtpParameters dictionary is constructed in more detail. by Taylor Brandstetter https://github.com/w3c/webrtc-pc/commit/be6c9c9b8cc2ec9806a27626084b09e61aa162f2 * Merge pull request #1134 from taylor-b/issue_1073_sendEncodings_take2 Add more detail about how getParameters and setParameters work. by Daniel Burnett https://github.com/w3c/webrtc-pc/commit/320def5e8baa1b58ce9894c1efc1e610e35f4928
Received on Thursday, 25 May 2017 14:11:39 UTC