How to add tracks during negotiation about libdatachannel HOT 3 OPEN

This is indeed an incorrect implementation in libdatachannel. The issue is with tracking the negotiation needed state: currently, it is too simplistic, the library sets a flag when adding a track and clears it when setLocalDescription() is called. As a result, when concurrent events happen, a track may be left non-negotiated, but the library forgets negotiation is needed. I'm looking into it.

from libdatachannel.

@daweifeng The specification forbids adding new tracks in answers, you can only add new tracks in offers. You may however modify offered tracks in the onTrack() callback before answering.

from libdatachannel.

How about invoking addTrack() when peer B receives an offer from peer A? Should we add track after calling setRemoteDescription() and before setLocalDescription() ? This is for a scenario that peer B might want to open a track that has a different name from the one open by A.

from libdatachannel.