Closed
Bug 1974443
Opened 5 months ago
Closed 4 months ago
Move RTCDataChannel's attributes to the DOM representation (currently nsDOMDataChannel)
Categories
(Core :: WebRTC: Networking, task, P2)
Core
WebRTC: Networking
Tracking
()
RESOLVED
FIXED
143 Branch
| Tracking | Status | |
|---|---|---|
| firefox143 | --- | fixed |
People
(Reporter: bwc, Assigned: bwc)
References
Details
Attachments
(1 file)
The necko DataChannel is currently the sole source of truth for various attributes on RTCDataChannel. This does not really mesh with the spec (these things are supposed to be updated in queued tasks), and will mesh even more poorly when RTCDataChannels can live on workers. The DOM object (which we ought to rename to RTCDataChannel while we're at it) should be where this information lives primarily. This will involve setting up the proper queued task updates, will probably involve changes to how stats are gathered, and various webidl fixes.
|
Assignee | |
Comment 1•4 months ago
|
||
Pushed by bcampen@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/e2e05dd5ece0
https://hg.mozilla.org/integration/autoland/rev/051816204819
Move DOM slots to RTCDataChannel r=ng
|
||
Comment 3•4 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 months ago
status-firefox143:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch
|
||
Updated•3 months ago
|
QA Whiteboard: [qa-triage-done-c144/b143]
You need to log in
before you can comment on or make changes to this bug.
Description
•