Closed Bug 1231414 Opened 8 years ago Closed 5 years ago

RTCPeerConnection.addTrack should not require a stream to be passed


(Core :: WebRTC, defect, P2)




Tracking Status
firefox45 --- wontfix
firefox67 --- fixed


(Reporter: bzbarsky, Assigned: bwc)



(Keywords: dev-doc-complete, Whiteboard: [spec])


(2 files)

Per calling addTrack with no streams should be OK.
Component: DOM → WebRTC
See Also: → 1271669
Rank: 25
Priority: -- → P2
Whiteboard: [spec]
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Rank: 25 → 15
Priority: P3 → P2

This is turning into a major headache with web-platform-tests, requiring lots of tests (that aren't really testing addTrack) to be disabled.

Assignee: nobody → docfaraday
See Also: → 1514670

Review ping.

Flags: needinfo?(jib)

All reviews here look accepted.

Flags: needinfo?(jib)
Pushed by
Part 1: Allow addTrack without a stream argument. r=jib,smaug
Part 2: Mark some wpt as expected to succeed. r=jib
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67

Documentation updated:

I've made substantial revisions to the article on addTrack() to cover this and to explain in more detail the relationship between the tracks and streams across a peer connection. This would definitely benefit from a review:

I've also made affiliated revisions to the following articles. Some are error corrections, some are clarifications, and there are a few additions of missing details:

Since this is a bug fix, I don't think it warrants a BCD update. If there's disagreement, it could be added as a note -- I'm not sure adding a "feature" row for this makes sense given that it's a bug fix.

Added to Firefox 67 for developers.

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