Re: [webrtc-pc] addTransceiver woes

> 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."


> "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 using your GitHub account

Received on Wednesday, 3 January 2018 22:30:25 UTC