Re: [webrtc-pc] addIceCandidate may not need to throw an error when no remoteDescription (#2519)

@Sean-Der Please show me a simple example demonstrating the problem.

> > most queuing I've seen only works on initial negotiation
> This is all I am looking for! I think after the initial negotiation all the logic stays the same.

The same methods and logic are used on renegotiation, so we have to think about that as well. E.g.
* App adding new tracks for a participant or screen-sharing sends additional ICE candidates
* App defers adding tracks until after initial negotiation
* App restarts ICE e.g. after connection failure
* App stops a BUNDLE transceiver

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at using your GitHub account

Received on Thursday, 30 April 2020 20:15:32 UTC