Originally Posted by sv1cec

Master Coder, you are the expert not me. What I am trying to say, is that now, we know what the problem is, and a way to avoid it: click in the box before you start typing.

Disabling the typing box on slow connections will create more problems than it will solve, because most of the time, the users will not be able to type. That will make the chat unusable for them. Of course, we could run some tests with dial-up users and see, but somehow I think it wouldn't be good.

I would suggest that you print a warning for IE 6 users, explaining what the problem is, and letting them take it into account. It's not a program's bug as it is evident by users of Firefox, Netscape and even IE5, it's an Explorer issue, so they have to learn how to use the program with that browser. What I'll do on my board, tonight, is to put a message which will say to the users how to avoid the problem, and how to stop it if it starts. From then on, they are on their own.

Rgds

Originally Posted by wirewolf

I just tried experimenting with some of my members, two on fast connections, one on a dial up, and one member on DSL. We tried using varied browsers, logging in and out. The dial up member said that the refresh of 8 seconds was too fast for him, and that he was, using IE6, but it didn't recreate the problem stated above. Go figure!
I upped the refresh to 15 seconds, and they all agreed that it was better.

Just a thought. Could you add a conditional to check for IE6 (and possibly a slow connection?), and if true, disable or up the refresh rate automatically. Then show a manual java refresh button or link for the user with the IE6, and display a instruct message on what to do at the bottom of the screen for said user?

One thing I did was to add a small table at the bottom of the Chat Room with some mini instructions and a tip or two. See attachment. I'm going to edit and add some of the Commands from the Help Page to this table.

John