|
Bugzilla – Full Text Bug Listing |
| Summary: | Remote GWIM client keeps seeing "User is typing message" when chat window is closed | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Bavo De Ridder <bderidder> |
| Component: | KDE | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | forgotten_jfl1mIJ7Fe |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bavo De Ridder
2005-09-14 09:09:35 UTC
Sorry, forgot to say this was in Kopete and the remote GWIM client was a native windows GWIM client. 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? let's see we have more important things in the queue ;( "say" of course |