1763716 - Offer with rejected m-line does not fire onremovetrack event, and currentDirection isn't stopped

Status: NEW

(Core :: WebRTC: Signaling, defect, P3)

Description

[Back Aug 24 [:jib]]

+++ This bug was initially created as a clone of Bug #1728367 +++

When we receive an offer with a rejected m-line, the spec says among other things that we must fire onremovetrack on any associated streams the transceiver.receiver.track is in.

Google and Edge appear to do this correctly (though their event firing order seems off a bit). Firefox and Safari do not.

STR:

• Open https://jsfiddle.net/jib1/76c1hogy/
• Click Start followed by Reject

Expected result:

ontrack
ontrack
onremovetrack
video transceiver currentDirection = recvonly
audio transceiver currentDirection = stopped
onended

Actual result:

ontrack
ontrack
video transceiver currentDirection = recvonly
audio transceiver currentDirection = null
onended

Workaround

• Listen for the ended event on the track instead of removetrack on its stream.