Fix errors external/wpt/RTCPeerConnection-removeTrack.https.html.
This is in preparation for RTCRtpTransceiver/Unified Plan support. "Calling removeTrack with valid sender should set sender.track to null" Asserting that direction changes from 'sendrecv' to 'recvonly', this is explicit in the spec[1]. "Calling removeTrack with currentDirection blah should set direction to blah" The tests that meant to set up currentDirection to be 'sendrecv' or 'recvonly' before removeTrack() were incorrect. Tests updated to set up currentDirection correctly. Also updated them to use async/await because that's much nicer. These all fail because we don't have transceivers yet, but when running these changes in the RTCRtpTransceiver WIP CL[2], they all pass. [1] See step 10 of https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-removetrack [2] https://chromium-review.googlesource.com/c/chromium/src/+/1025771/ Bug: 777617 Change-Id: Ie3c077d14ea30038a06a98ecbeea475ac824dd9c Reviewed-on: https://chromium-review.googlesource.com/1095275Reviewed-by:Guido Urdaneta <guidou@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#566366}
Showing
Please register or sign in to comment