[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 20:13:19 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=33248
--- Comment #16 from Fumitoshi Ukai <ukai at chromium.org> 2010-02-03 20:13:17 PST ---
(In reply to comment #13)
> (From update of attachment 47998 [details])
> Nice test! r=me
>
> > + WebSocket should close the connection when unloading the document
>
> One thing I'm not quite sure about - how does the HTML5 "unload the document"
> concept correspond to detaching a frame?
I think iframe constructs a nested browsing context, so removing it would cause
"unload the document"..
> Maybe we should make one or two more
> variations of this test - in one, we'd force garbage collection after detaching
> subframe;
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 ?
> 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?
--
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