Bug 104734

Summary: Threaded message display not correctly updated after new messages downloaded
Product: [Unmaintained] knode Reporter: Tristan Miller <psychonaut>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Showing results as at step #8
Expected behaviour as at step #8

Description Tristan Miller 2005-04-28 22:19:21 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs

Steps to reproduce:

1. Open a newsgroup.  Make sure you are in threaded view.
2. Search for something using the Quick Search bar.
3. Expand a thread.
4. Select a leaf message (i.e., one without any replies)
5. Reply to said message.
6. Allow enough time for your post to reach the news server.
7. Right-click on newsgroup name; select "Get New Articles"

Observed behaviour:

8. The selected leaf message becomes a non-leaf with the "-" button beside it, indicated that it has a reply and that the thread is open (i.e., not collapsed).  However, the reply is not shown in the message list.
9. If the "-" button is clicked, it changes to a "+" and "(1)" appears after the subject.  However, if the "+" button is clicked again, the new reply is still not revealed; we get the same results as in step #8.

Expected behaviour:

8. The leaf message should become a non-leaf with the "-" button beside it, and the new reply should be inserted into the message list directly below.
                            -OR-
8. The leaf message should become a non-leaf with the "+" button beside it, and "(1)" should appear after the subject.  The user can click on the "+" to reveal the new reply.
Comment 1 Tristan Miller 2005-04-28 22:20:09 UTC
Created attachment 10840 [details]
Showing results as at step #8
Comment 2 Tristan Miller 2005-04-28 22:22:21 UTC
Created attachment 10841 [details]
Expected behaviour as at step #8
Comment 3 Rolf Eike Beer 2007-11-27 18:57:55 UTC

*** This bug has been marked as a duplicate of 76244 ***