Closed Bug 1767820 Opened 2 years ago Closed 1 year ago

Stop allowing addTrack to set the addTrackMagic bit in RTCRtpTransceiver

Categories

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

task

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: bwc, Assigned: bwc)

Details

Attachments

(1 file)

RTCRtpTransceivers created by addTrack are allowed to automatically associate with m-sections in a remote offer, as opposed to transceivers created with addTransceiver; this is referred to in our codebase as "addTrackMagic". Years ago, the spec authors intended to allow a subsequent call to addTrack to set this bit on a transceiver created by addTransceiver, but this never actually happened, and was never implemented in Chrome.

At this point, we probably need to remove this behavior, since it is unlikely it will ever make it into the spec.

Assignee: nobody → docfaraday
Attachment #9315412 - Attachment description: Bug 1767820: Only set addTrack magic for transceivers _created_ by addTrack. r?jib → Bug 1767820: Only set addTrack magic for transceivers _created_ by addTrack. r?mjf

Seeing some intermittents, double-checking for significant rate increases.

Try looks fine.

Attachment #9315412 - Attachment description: Bug 1767820: Only set addTrack magic for transceivers _created_ by addTrack. r?mjf → Bug 1767820: Only set addTrack magic for transceivers _created_ by addTrack. r?jib
Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8d6de9c29d1e
Only set addTrack magic for transceivers _created_ by addTrack. r=mjf
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: