cannot connect using Google Chrome even when limited to 'websocket' transport.

[aliasaria]

cannot connect using Google Chrome even when limited to 'websocket' transport.

[dexterdeng]

I got that issue too. any help?

[rustycar54]

I will have to look and see if I ended up doing anything special, but ISTR that somehow it started working with google chrome (and only Google Chrome) when I set the websocket/flashsocket limitation. (my transports says: transports: ['websocket', 'flashsocket'])

(The reason my reply took so long was that I did do a little looking just now and couldn't see anything obvious. (I added some new colors, and added buttons along the bottom to create cards of a single color rather than having to keep trying to get the color card we wanted. To do that is just a change to views/home.jade around line 20 where you copy/pasta_with_modify the line above into something like 'image#create-card-white.bottom-icon(width=...', then you go to client/script.js and copy/pasta_with_mod the $( "#create-card"...) stuff into $( "#create-card-white"...))

FWIW, I was running chrome 12.0.742.122 m, just updated to 13.0.782.220 m, which in my 5 minutes of testing seems to work fine also.

I am using npm and not socket.io. Also, I am using express 2.3.11 and connect 1.5.1, it appears. Not sure either of those matter, but there you have it.

Do you have any firewalls in the way?

Rusty

-----Original Message-----
From: dexterdeng [mailto:[email protected]]
Sent: Sunday, August 07, 2011 5:54 PM
To: Carruth, Rusty
Subject: Re: [scrumblr] cannot connect using Google Chrome even when limited to 'websocket' transport. (#25)

I got that issue too. any help?

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