- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Apr 2018 15:44:46 +0000
- To: public-webrtc-logs@w3.org
> This seems to indicate that prior to negotiation completing, the set should be empty. Is this intentional, and reasonable? Yes and yes. If you want to know the codecs the browser is capable of (and thus would offer) you can use `RTCRtpSender.getCapabilities`. `getParameters` is for what is available to send, so the application can pick one and put its payload type in `RTCRtpEncodingParameters`. Until a remote description is set, you don't know what payload types they'll use, so it wouldn't make sense to return anything. That's my two cents anyway. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1839#issuecomment-382041010 using your GitHub account
Received on Tuesday, 17 April 2018 15:44:51 UTC