- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jan 2018 22:29:47 +0000
- To: public-webrtc-logs@w3.org
> The sender has never been used to send. More precisely, the [[CurrentDirection]] slot of the RTCRtpTransceiver associated with the sender has never had a value of sendrecv or sendonly." and > "If track is null then the RTCRtpSender does not send." It seems we can have senders which do not send and yet have a [[CurrentDirection]] of sendrecv or sendonly? @jan-ivar i think you need to write another blog post ;-) -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-355146061 using your GitHub account
Received on Wednesday, 3 January 2018 22:30:25 UTC