- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2019 15:03:32 +0000
- To: public-webrtc-logs@w3.org
Discussion during meeting: - Somewhat related: ptime should be [at risk](https://github.com/w3c/webrtc-pc/issues/2311), if it is removed then we don't have to specify which value takes priority if both are specified. - The feeling was that this makes sense but that we should use a boolean. - Considering WebRTC 1.0 is reaching PR and features not implemented by multiple browsers are at risk, this should be defined in an extension spec. - To decide in the extension spec: Should this be a parameter (setParameters() on a per-sender basis) or an RTCConfiguration? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2309#issuecomment-535546639 using your GitHub account
Received on Thursday, 26 September 2019 15:03:34 UTC