[Webkit-unassigned] [Bug 184911] New: RTCRtpSender.replaceTrack(null) ends current track

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=184911

            Bug ID: 184911
           Summary: RTCRtpSender.replaceTrack(null) ends current track
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: seppe at vectera.com
                CC: youennf at gmail.com

According to the spec, adding and then removing a track from a RTCPeerConnection can be done as follows:

let pc = new RTCPeerConnection();
let sender = pc.addTrack(track, stream);

// Negotiate,...

sender.replaceTrack(null);



This works fine on Chrome and Firefox. On Safari however, the call to replaceTrack() stops the track entirely, setting readyState to "ended" (but interestingly, not calling the onended callback). This makes it impossible to use this method to remove a track that is still used elsewhere. This is problematic, especially since pc.removeTrack(track) is buggy as well: https://bugs.webkit.org/show_bug.cgi?id=174327


This example should demonstrate the issue: https://jsfiddle.net/vt55wx9u/4/.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180424/954e77df/attachment.html>