[webrtc-pc] onmute then onunmute can fire before negotiation completes

docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc:

== onmute then onunmute can fire before negotiation completes ==
Let's say we're renegotiating, and the offerer has muted a track using "recvonly" or "inactive" in the offer.

answerer.setRemoteDescription(offer) causes onmute to fire, but let's say an RTP packet for that track arrives, causing the track to be unmuted. Then negotiation completes (which definitively tells us that track is muted), but we don't fire onmute again.

Is this the desired behavior?

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1707 using your GitHub account