Open Bug 1568296 Opened 1 year ago Updated 4 months ago

Support stopping and stopped transceivers


(Core :: WebRTC, enhancement, P2)




Tracking Status
firefox70 --- affected


(Reporter: jib, Assigned: jib)


(Blocks 2 open bugs)


(Keywords: dev-doc-needed)

Per w3c/webrtc-pc#2220.

This solves the BUNDLE footgun, and in the process deprecates the JS-observable tc.stopped transceiver property in favor of a new "stopped" enum value in tc.direction and tc.currentDirection.

Firefox will likely continue to expose the stopped property for a release or two for backwards compatibility until we have telemetry numbers for it that justify deprecating it.

This is largely updated already in documentation, but there is some review to do, and IIRC I held off pulling the trigger on a few bits until it actually hit the spec proper. We may need to review some examples throughout content to change this.

On a related note, but not part of this work: we should review our documentation to start shifting some of it from using addTrack() to working with transceivers directly, as this is the new hotness.

Keywords: dev-doc-needed

Bugbug thinks this bug is a enhancement, but please change it back in case of error.

Type: defect → enhancement

Byron and I agreed it makes sense to tackle as well, as part of this work. That is: remove stopped transceivers from pc.getTransceivers() in SRD(offer).

Blocks: 1580301
Blocks: 1505509

Docs team: will not ship in 70.

You need to log in before you can comment on or make changes to this bug.