Open
Bug 668948
Opened 13 years ago
Updated 2 years ago
Websockets events happen out of order if client handlers do Sync XHR
Categories
(Core :: Networking: WebSockets, defect, P3)
Tracking
()
NEW
People
(Reporter: jduell.mcbugs, Unassigned)
Details
(Whiteboard: [necko-backlog])
Attachments
(1 file)
|
2.76 KB,
patch
|
jduell.mcbugs
:
review+
|
Details | Diff | Splinter Review |
We realized this was an issue for e10s WS in bug 537787, which fixed this for e10s. But test exposed that non-e10s is busted, so we need to fix it. The issue in a nutshell: onclose() is getting called before (possibly during?) onmessage() if we put syncXHR calls in the client handlers. Edge case, but needs to be fixed.
Attachment #543571 -
Flags: review+
fwiw, we have these types of bugs in almost everything.
This is quite a old bug, but it is always in the latest version of FF (21). Do you plan to correct it ?
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog]
|
||
Comment 3•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 4•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•