- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Jun 2017 16:37:50 +0000
- To: public-webrtc-logs@w3.org
Since this is only around for backwards compatibility, creating a transceiver as a side-effect seems like an acceptable option. It would only negatively affect people who don't do `setLocalDescription` after `createOffer({offerToReceiveAudio: true})`.
> how many weeks would it take you to get number of "createOffer is called with offerToReceive* a second time with offerToReceive* without a setLocalDescription in between" (assuming you can measure that)?
If `createOffer({offerToReceiveAudio: true})` creates a transceiver, then to address this we'd just need to change:
> the existing localDescription (if any) doesn't contain any sendrecv or recv audio media sections
To:
> *connection* has no non-stopped "sendrecv" or "recvonly" audio transceivers
--
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1383#issuecomment-308797360 using your GitHub account
Received on Thursday, 15 June 2017 16:37:57 UTC