- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2024 12:37:50 +0000
- To: public-webrtc-logs@w3.org
> Doesn't that make more sense somehow? JSEP says we MUST NOT do that. I assume the reason is that the answerer could interpret such codecs as codecs we are willing to receive. I've addressed the SLD failure from https://jsfiddle.net/fippo/r63bp8d2/2/ with my change, turned out to be a fairly trivial implementation issue. The new behavior if you set a receive-only codec via sCP and set the direction to sendonly is that the transceiver is stopped by SLD. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2932#issuecomment-1934030111 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 February 2024 12:37:53 UTC