[Webkit-unassigned] [Bug 33248] WebSocket should close the connection when unloading the document

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 3 23:11:19 PST 2010


--- Comment #19 from Fumitoshi Ukai <ukai at chromium.org>  2010-02-03 23:11:17 PST ---
(In reply to comment #18)
> > I'm not sure what it is trying to test. set event handler to websocket in frame
> > (like websocket-pending-activity.html?) and detaching subframe and force
> > garbage collection and see it would get onmessage ?
> I think it will get stopped, just testing that it won't crash.

Ah, I see.

> >> in another, we'd keep a reference to frames[0].document, making sure
> >> that it outlives the frame.
> > this means websocket object is kept in parent document of the frame and see it
> > won't be closed after detaching the frame?
> I was thinking about a reference to an object from child context. Again, just
> to see that it's not crashing (which is of course so, since detaching the frame
> will stop network activity, and nothing will happen to the object).
> Another variation:
> // in subframe
> top.ws = new WebSocket;
> // in parent frame
> // ...detach subframe
> ws.open(...)

Ok.  https://bugs.webkit.org/show_bug.cgi?id=34562

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list