TeaChat

Problem: Webkit browsers fire their events too soon - so things like 'onkeyup' intermittently break because the event keycode hasn't been set yet depending on what else the computer is doing.

Symptom: You can see this in the chat window when people with those browsers type and it thinks they have pressed 'enter', so it posts the chat frequently when they haven't actually hit 'enter' resulting in fragmented and often single character posts. It's really really annoying. Webkit browsers constitute around 20% of the browsers on the internet and Chrome in particular is growing faster than anyone. So your chat script is annoying 20% of your user base.

Possible Solution:

Currently the chat text input html element has the property shown below
This is what is breaking on webkit browsers - to ensure the event get's called _after_ the page is updated and the event keycode is set you wrap it in a timeout set to zero.

replace above with:
and everything works properly for webkit browsers. (tested on chrome for a while by editing the html in the browser and didn't see the problem once after the edit went in) Your mileage may vary, but it seems like a relatively simple fix with a large positive impact.


Thanks!

Thanks, Tenuki!

This fixes it for me, hope it makes it into the site.

it's annoying way more than 20% of the users... it's a PITA for both us "alt-browser" users, AND for everyone who has to try to read it.

I don't really understand the content of your post, is this something we can do ourselves in the browser window before using chat? or is this a fix that can only be applied at the adagio end? (sorry for the n00b question)

I've updated the code. Please let me know if the IM is better behaved.

Geekgirl wrote:it's annoying way more than 20% of the users... it's a PITA for both us "alt-browser" users, AND for everyone who has to try to read it.

I don't really understand the content of your post, is this something we can do ourselves in the browser window before using chat? or is this a fix that can only be applied at the adagio end? (sorry for the n00b question)

both. if you select the text box element in chrome and choose 'inspect element' from the contextual menu you can make the change to your browsers html and it will work - but next time you reload/refresh the page it will be back to the old stuff.

long term fix is to fix it at teachat's end - which it appears Ilya has already done.

ilya wrote:I've updated the code. Please let me know if the IM is better behaved.

yeah!

tenuki wrote: both. if you select the text box element in chrome and choose 'inspect element' from the contextual menu ...

thanks! I have one more forum where this is broken. I'll be able to use it there.

OK, it seems perhaps this fix is wreaking havoc for IE.

Several things are not working coincidently after the fix. Pressing enter to enter an IM post does not work.

Also after clicking post, one must now left click on the box in order to begin typing the next entry ...

Also, I get this effect a lot ...

a
h
c
n
e
s

Thus having to refresh quite frequently (which also causes loss of work if posting a reply on the forum ... and forget to save).

A real pain!!!!!!!!!!

So, has the fix broken the IM for IE users??? Seems so.

Please let me know if the new IE bug has been resolved.

ilya wrote:Please let me know if the new IE bug has been resolved.

Nope ...

how about now?

did for a sec ... and then not.

What version of IE?

8.0

The problem appears to be remedied.