[Webkit-unassigned] [Bug 87336] [WebSocket] WebSocket object should fire error event when WebSocket server can't be connected.

[bugzilla-daemon at webkit.org]

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





--- Comment #11 from Li Yin <li.yin at intel.com>  2012-05-31 07:14:40 PST ---
Currently this patch aims to fix the issue only for chromium platform.

There is a related bug in chromium to track this issue.
http://code.google.com/p/chromium/issues/detail?id=128057
And I have already uploaded the chromium-side patch.

Some main changes are listed as followed:
Chromium side:
1. Add OnError function in SocketStreamDispatcherHost Class, send the Error Message to SocketStreamDispatcher.
2. Add OnFailed function in SocketStreamDispatcher Class, handle the Error Message from SocketStreamDispatcherHost.
3. Add OnError function in WebSocketStreamHandleBridgeImpl, let DumpRenderTree can work like Browser.

WebKit side:
1. Change the behavior of didFail, call didFailSocketStream instead of didCloseSocketStream.

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