Hiroshi Ichikawa
Hiroshi Ichikawa
Try [Troubleshooting](https://github.com/gimite/web-socket-js#troubleshooting) section of README and let me know the result of each step. It is often especially useful to try an environment with native WebWocket support like Chrome. Just...
As mentioned above, it is often helpful to try it with Chrome to see if it works. I'm not so sure but I guess self-signed certificate is rejected by default,...
Maybe something in-between (like a router) disconnected the TCP connection? Disconnection can happen (e.g., the network can be disconnected), and the application should somehow handle it (reconnect automatically, show an...
That looks like a packet sent from the server.
Thanks for the report. The change itself looks good because performance improved in most browsers. It would be nice to fix the Opera issue, though.
Hm, maybe issue of Opera itself...?
onclose event is fired in my environment with a server using em-websocket. What WebSocket server do you use? Possible reasons I can think of: - You call close() on WebSocket...
Thanks for the patch and sorry for late. I'll take a look soon.
I tried sending "foo\0bar" to IE9 and it was handled correctly. Have you tried the same code with Chrome? If it happens in Chrome too, it's likely that your server...
I found that IE9 doesn't define either document.createEvent nor window.MessageEvent. So usually it doesn't go to code path using document.createEvent in IE9 anyway. Maybe one of the libraries you are...