Bug 116931 - Remote GWIM client keeps seeing "User is typing message" when chat window is closed
Summary: Remote GWIM client keeps seeing "User is typing message" when chat window is ...
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: KDE (show other bugs)
Version: RC 1
Hardware: Other All
: P5 - None : Minor
Target Milestone: ---
Assignee: Will Stephenson
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-14 09:09 UTC by Bavo De Ridder
Modified: 2006-02-09 21:11 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bavo De Ridder 2005-09-14 09:09:35 UTC 
Remote GWIM client keeps seeing "User is typing message" when chat window is 
closed that contained a message ready to be send but that was not send.
Comment 1 Bavo De Ridder 2005-09-14 09:10:15 UTC 
Sorry, forgot to say this was in Kopete and the remote GWIM client was a 
native windows GWIM client.
Comment 2 Will Stephenson 2005-09-14 12:03:09 UTC 
Mike: 
 
The Windows client gets stuck on "User is typing a message" if Kopete closes 
the chatwindow while the user is typing.  I haven't been able to reproduce but 
I'd guess that kopete can send UserTyping then leaveconf which confuses the 
Win client.  Does this sound likely? 
 
Intuitively, if a client gets a ConferenceLeft from a typing user, it should 
clear the typing state, this would save us a round trip to the server to 
explicitly state that we are not typing before sending the leaveconf.  Do you 
think this is possible to implement on other platforms?
Comment 3 Stephan Kulow 2006-02-09 21:10:50 UTC 
let's see we have more important things in the queue ;(
Comment 4 Stephan Kulow 2006-02-09 21:11:11 UTC 
"say" of course