Make WebSocket.close() prevent any more events from firing

NEW
Unassigned

Status

()

Core
Networking: WebSockets
P3
normal
6 years ago
a month ago

People

(Reporter: sicking, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog])

This is a recent change to the spec, so I assume that we don't yet do this:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14474

The idea is that once someone has called .close() on a websocket, we ensure to not fire any more message events on that socket. This means that any events received from the server after sending the closing frame, as well as any events which we had already received but not yet fired the DOM event for, should be suppressed.
Moving this to networking:websockets, just because the folks (right now, me) who are working on this kind of stuff are a lot more likely to follow it if it's there.  Reassign back if you object, jonas.
Component: DOM → Networking: WebSockets
OS: Mac OS X → All
QA Contact: general → networking.websockets
Hardware: x86 → All
Would this help with bug 694519?
No, since no-one is calling .close() in that testcase it's entirely unrelated.
Whiteboard: [necko-backlog]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.