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

Status: NEW

(Core :: Networking: WebSockets, defect, P3)

Description

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

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.

Comment 1

[Jason Duell]

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.

Comment 2

[Dirkjan Ochtman (:djc)]

Would this help with bug 694519?

Comment 3

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

No, since no-one is calling .close() in that testcase it's entirely unrelated.

Comment 4

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 5

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258