[Webkit-unassigned] [Bug 34636] WebSocket close() causes a task to be queued to fire a close event

[bugzilla-daemon at webkit.org]

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





--- Comment #2 from Fumitoshi Ukai <ukai at chromium.org>  2010-02-05 02:00:44 PST ---
On WebKit nightly build, WebSocket close() method calls onclose event handler
synchronously, but WebSocket API spec says

The close() method must close the Web Socket connection or connection attempt,
if any, and change the readyState attribute's value to CLOSED (2). If the
connection is already closed, it must do nothing.

Closing the connection immediately causes a task to be queued to fire a close
event, as described below.

So, running WebKitTools/Scripts/run-webkit-tests on attached layout tests fails
for now.

Chromium works as expected.

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