Open
Bug 712173
Opened 13 years ago
Updated 3 years ago
Websocket.send should only throw for certain errors
Categories
(Core :: Networking: WebSockets, defect, P5)
Core
Networking: WebSockets
Tracking
()
NEW
People
(Reporter: jduell.mcbugs, Unassigned)
Details
(Whiteboard: [necko-backlog])
Right now we return error codes for lots of things that go wrong in Send. The spec says only that we should throw if we're CONNECTING, or if the data argument has any unpaired surrogates,. So we should change other error cases to fail the websocket and return NS_OK.
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog]
|
||
Comment 1•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Comment 3•3 years ago
|
||
Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: P3 → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•