"cancel" that becomes "close"

[zloba_org]

in the chat window, when i hit "Send" and it's in the process of sending the message, "Send" becomes disabled, and "Close" becomes "Cancel". IMHO this is a rather bad idea - here's a scenario (it actually happened once or twice), and i keep expecting it to happen again.

[ What is the point of this transformation anyway? A radical change in function that occurs asynchronously = bad idea ]

I am sending the first message to a user with a slow connection, high latency. I hit send ("Send through server" is Off) - it starts sending it. Then, i start thinking they're behind firewall, and try to cancel it, enable "Send through server" and "Send" again.

However, just as i hit "Cancel", the message does come through, the button becomes "Close" again, and the window gets closed. ARGH!

I would suggest either:

- let "Send" become "Cancel". If the message suddenly comes through, the field will be cleared so nothing bad will happen.

- make a separate "Cancel" button. If the message comes through, it will become disabled, and in any case won't do nothing unexpected. I'd prefer this one.

+ In any case, i'd disable input field while sending (and every other button as well), so that the user cancels explicitly before doing anything else, lest any text becomes lost, or any other surprises happen.

[dreamforce2]

Logged In: YES user_id=527951

Thanks for your report, i'll have a look at it. Thomas

[zloba_org]

Logged In: YES user_id=1158242

had this sitting in my build directory for a year

[zloba_org]

Logged In: YES user_id=1158242

i was referring to the attached patch - licq.patch.close

[erijo]

Fixed in [4452].

[zloba]

wonderful, thanks! (tried in 1.3.4RC1 - looks good)

[anonymous]

Milestone 1.3.4 deleted