On Chromium port, WebSocket.onclose() callback doesn't be called when JavaScript call close() before onopen() is called. Current test to check this scenario, access to ws://127.0.0.1:8880/websocket/tests/hybi/handing-handshake. This URL cause close event by another reason, so the problem is hidden by chance.
Created attachment 104650 [details] Patch
(In reply to comment #1) > Created an attachment (id=104650) [details] > Patch Do you need review? The review flag is not set.
Thank you for comment. I'll check it in Chromium if this test reproduce the issue. After that, I'll check the review flag. Thanks!
DumpRenderTree/chromium passes this test because its IPC implementation is different from one of chromium itself. But, manual test by Chrome fails. So I think it's worth to submit.
Comment on attachment 104650 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=104650&action=review > LayoutTests/platform/chromium/test_expectations.txt:173 > +// Temporally disable until WebSocket IPC bug is fixed. > +BUGCR93698 SKIP : http/tests/websocket/tests/hybi/close-before-open.html = PASS TIMEOUT FAIL > + You said DRT/Chromium passed this test. So we don't need this part.
Created attachment 104652 [details] Patch
Comment on attachment 104652 [details] Patch ok
Comment on attachment 104652 [details] Patch Clearing flags on attachment: 104652 Committed r93505: <http://trac.webkit.org/changeset/93505>
All reviewed patches have been landed. Closing bug.