- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jun 2017 16:01:25 +0000
- To: public-webrtc@w3.org
docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc: == Checks for negotiation-needed are underspecified when currentLocalDescription/currentRemoteDescription are not set == The following language does not work if the PC has not performed an initial negotiation. (Transceivers are expected to be associated before offer/answer completes, so this language can apply in this situation) " - If t's direction is "sendrecv" or "sendonly", and the associated m= section in connection's currentLocalDescription doesn't contain an "a=msid" line, return "true". - If connection's currentLocalDescription if of type "offer", and the direction of the associated m= section in neither the offer nor answer matches t's direction, return "true". - If connection's currentLocalDescription if of type "answer", and the direction of the associated m= section in the answer does not match t's direction intersected with the offered direction (as described in [JSEP] (section 5.3.1.)), return "true". " Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1375 using your GitHub account
Received on Monday, 12 June 2017 16:01:31 UTC