when i click stop in the browser it disconnects from now

[shimondoodkin]

intuitive behavior anti pattern:
somehow web sockets io decided to use XHR , i saw an hourglass cursor very long time , so i clicked stop
(because i saw the page is loaded fully but it still tells me to wait).
when i click stop in the browser it disconnected the page from now.
then i clicked in the simple chat on send message button and it did not worked.

at last i expected it to reconnect and execute the send message request. + maybe to preserver the client id and maybe maybe to execute the stack of unsent commands that is kept for some time on the server.

other solution is to change the cursor to default.

[3rd-Eden]

Was it a webkit based browser?

[shimondoodkin]

it was a chrome i installed a week ago.

[3rd-Eden]

If now js updates to latest socket.io version this would be resolved

~ Arnout Kazemier

On Jun 2, 2011, at 12:33 AM, shimondoodkinreply@reply.github.com wrote:

it was a chrome i installed a week ago.

Reply to this email directly or view it on GitHub:
#94 (comment)

[shimondoodkin]

thanks

[ericz]

Thanks 3rd-Eden we'll test and bump up the version number =p

[3rd-Eden]

Be sure to check if it solved this issue ;). But my I guess so as the in 0.6.17 the XHR connection was made before onload in webkit based browser which triggers the load indicators even when the browser is finished loading.. And pressing top always causes all current requests to top..

[shimondoodkin]

this issure is resolved