Firefox won't work again until restarted on server restart about now HOT 12 CLOSED

Nice find! I'll look into this tonight.

Thanks

from now.

Well we can definitely reproduce the bug. Still debugging...

from now.

any updates? I get serious problems with Firefox..

20 Mar 15:27:21 - Initializing client with transport "xhr-multipart"
20 Mar 15:27:21 - Client 07681131735444069 connected

then nothing, on now.ready I'm calling things - no response!

from now.

I can add more clarity to this bug: it seems that socket.io isn't working well with different clients using different transports. If your first attendant logs into the room with Safari 5.0.4 on a mac, safari-safari chats work fine. If your second attendant logs in with firefox (3.6.13), safari-safari chats continnue to work, but firefox users can neither send nor receive messages. Similarly, if you log in with chrome (10.0.648.151), chrome users can send messages, but don't get to receive messages (from themselves or from anyone else). Each client mentioned uses a different transport - I'm not sure if that's a part of the problem.

from now.

any news on this?

from now.

hey Keyle and ssebro

I have been able to replicate some of these bugs. The key seems to be when xhr-polling and xhr-multipart are involved, weird things happened with regards to connect and disconnect events.

It seems like the issues are with the Socket.IO library we depend on. I know a major version release for Socket.IO is coming so hopefully these issues are fixed.

Also xhr-multipart/xhr-polling in Firefox are fallbacks to the prefered Flashsocket method (if the user has Flash installed).

Keyle, I'm guessing this has something to do with the cookie which stores chosen transport method. The weird part is the clientId in socket.io doesn't change.

I'm going to wait a bit more for v0.7 to come out to see if this issue is fixed. I can't replicated this consistently so I'm not sure the next steps to take.

from now.

Ok thanks Eric.

from now.

Yeah, thanks a lot - I appreciate you following up.

from now.

Hey guys,

3rdEden messaged me on Twitter and he was having trouble reproducing these bugs. Using the latest version of nowjs, socket.io, and respective browsers I haven't been able to reproduce them anymore either.

Additionally he mentioned v0.7 of socket.io probably won't include updates that are related to the problems we're seeing.

I'm going to test some more with different versions but I believe the issues may be fixed already in the latest versions of everything? I am not sure whether the original bug was in NowJS (may very well be) or socket.io or browsers, but I am unable to reproduce them anymore

from now.

I agree, I just fired it up on all three (ffox, safari, chrome) and did chat fine... Seems fixed to me...

from now.

Maybe we can have Keyle test on his machine and close this as unable to reproduce?

from now.

Closing

from now.