RTCDataChannel.id logic needs an overhaul
Categories
(Core :: WebRTC: Signaling, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: bwc, Assigned: bwc)
References
Details
Attachments
(4 files, 1 obsolete file)
Our implementation of DataChannel only assigns ids after the stream id limit has been successfully negotiated in SCTP. The webrtc-pc spec says to set these immediately, and make a best effort to negotiate the stream limit so they can be used. We need to update our code to implement this best-effort approach.
Assignee | ||
Comment 1•5 years ago
|
||
Given that this difference leads to lots of buggy behavior, I think I'm going to call this a defect.
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Depends on D35046
Assignee | ||
Comment 7•5 years ago
|
||
Depends on D35047
Assignee | ||
Comment 8•5 years ago
|
||
Depends on D35048
Assignee | ||
Comment 9•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 10•5 years ago
|
||
Assignee | ||
Comment 11•5 years ago
|
||
Comment 12•5 years ago
|
||
Comment 13•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/112937d690e0
https://hg.mozilla.org/mozilla-central/rev/f8ce8930bcab
https://hg.mozilla.org/mozilla-central/rev/a87072937e2c
https://hg.mozilla.org/mozilla-central/rev/05898e5d5434
Comment 14•5 years ago
|
||
Backed out 4 changesets (bug 1556795)for causing RTCPeerConnection-createDataChannel.html to perma fail
push that caused the backout: https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception&classifiedState=unclassified&revision=05898e5d54344e2e43181bfe6608b029771e39af
backout: https://hg.mozilla.org/integration/mozilla-inbound/rev/cb03b8da2fbfc316a70b836d77483f8971c7fd8b
Assignee | ||
Comment 15•5 years ago
|
||
Looks like this collided with 1558851.
Assignee | ||
Comment 16•5 years ago
|
||
Yeah, it looks like the merge didn't go quite right here.
Updated•5 years ago
|
Comment 17•5 years ago
|
||
Oh sorry I was just preparing a patch to fix the metadata, but understandably the sheriffs decided to back out. I think the right patch is something like
diff --git a/testing/web-platform/meta/webrtc/RTCPeerConnection-createDataChannel.html.ini b/testing/web-platform/meta/webrtc/RTCPeerConnection-createDataChannel.html.ini
index b4dd12fbec66..c40c1ddaa60c 100644
--- a/testing/web-platform/meta/webrtc/RTCPeerConnection-createDataChannel.html.ini
+++ b/testing/web-platform/meta/webrtc/RTCPeerConnection-createDataChannel.html.ini
@@ -43,6 +43,3 @@
expected: FAIL
bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1550497
- [Channels created (after setRemoteDescription) should have id assigned]
- bug: https://bugzilla.mozilla.org/show_bug.cgi?id=797135
- expected: FAIL
Assignee | ||
Comment 18•5 years ago
|
||
Yeah, I'm rebasing and rebuilding now. Should be able to re-land later today.
Assignee | ||
Comment 19•5 years ago
|
||
Comment 20•5 years ago
|
||
Comment 21•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/947f43a8a712
https://hg.mozilla.org/mozilla-central/rev/64c2df149745
https://hg.mozilla.org/mozilla-central/rev/ea730cd703a2
https://hg.mozilla.org/mozilla-central/rev/fb1e149d91bf
Updated•5 years ago
|
Comment 22•5 years ago
|
||
I would suggest to wait until https://github.com/w3c/webrtc-pc/pull/2222 has been merged. This should drastically simplify things.
Description
•