- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Jun 2017 14:54:54 +0000
- To: public-webrtc-logs@w3.org
Whether createOffer internally creates a transceiver is not very clear from the [spec language](http://w3c.github.io/webrtc-pc/#dom-rtcofferoptions-offertoreceiveaudio) IMHO:
*"When this is given a non-false value, no outgoing track of type "audio" is attached to the PeerConnection, and the existing localDescription (if any) doesn't contain any sendrecv or recv audio media sections, createOffer() will behave as if addTransceiver("audio") had been called once prior to the createOffer() call. "*
In the narrowest interpretation, this statement only modifies createOffer's behavior: to act as it would have acted had addTransceiver() been previously called. This to me does not say it acts as addTransceiver.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1383#issuecomment-308143205 using your GitHub account
Received on Tuesday, 13 June 2017 14:55:00 UTC