Open
Bug 1413198
Opened 7 years ago
Updated 2 years ago
Closing a data channel directly after sending discards pending data
Categories
(Core :: WebRTC: Networking, defect, P3)
Core
WebRTC: Networking
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox58 | --- | affected |
People
(Reporter: lgrahl, Unassigned)
Details
Attachments
(1 file)
8.64 KB,
text/html
|
Details |
https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-13#section-6.7 states that "[RFC6525] also guarantees that all the messages are delivered (or abandoned) before the stream is reset." This doesn't seem to be the case for Firefox. You can test the behaviour in the attachment I've uploaded or here: https://lgrahl.de/examples/dc/dc-test-send-close.html
Comment 1•7 years ago
|
||
Discarding data sounds bad. Nils, could you make a more refined triage? Low P2 for now.
Rank: 18
Flags: needinfo?(drno)
Priority: -- → P2
Comment 2•7 years ago
|
||
As Randell pointed out in #media I think this first of all needs clarification in the W3C specs to describe what should happen with the data. Although I think that we all agree on what should be done here (attempt to send the remaining data, before closing), I would like to see at least spec issue where people appear to agree on that solution, before we start implementing a solution. Lowering priority until we have that clarification.
Flags: needinfo?(drno)
Priority: P2 → P3
Updated•7 years ago
|
Rank: 18 → 25
Reporter | ||
Comment 3•7 years ago
|
||
I've opened an issue for the closing procedure: https://github.com/w3c/webrtc-pc/issues/1699
Reporter | ||
Comment 4•7 years ago
|
||
It also doesn't look like the channel is being closed for the remote peer...
Reporter | ||
Comment 5•6 years ago
|
||
This has been resolved in the spec now. I think we can proceed. :)
Flags: needinfo?(drno)
Comment 6•6 years ago
|
||
Right now I don't think this high enough for one of our engineers to work on any time soon. But if you are volunteering to fix this that would be awesome! :-)
Flags: needinfo?(drno)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•