Closed
Bug 1531148
Opened 6 years ago
Closed 6 years ago
RTCPeerConnection-setRemoteDescription-tracks.https.html wpt expects remote and local track ids to match
Categories
(Core :: WebRTC: Signaling, enhancement, P2)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
mozilla67
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: bwc, Assigned: bwc)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Remote track ids don't have anything to do with the track ids on the other side as of the latest spec, meaning that several test-cases in here are broken.
|
Assignee | |
Updated•6 years ago
|
Rank: 16
|
|
Assignee | |
Updated•6 years ago
|
Assignee: nobody → docfaraday
|
|
Assignee | |
Comment 1•6 years ago
|
||
|
|
Assignee | |
Comment 2•6 years ago
|
||
|
|
Assignee | |
Comment 3•6 years ago
|
||
Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2c058bf08a51
Fix some test-cases that expect local and remote track ids to match, and re-enable those test-cases. r=jib
|
||
Comment 5•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/15855 for changes under testing/web-platform/tests
You need to log in
before you can comment on or make changes to this bug.
Description
•