Closed
Bug 125987
Opened 23 years ago
Closed 22 years ago
Threading is wrong after receiving new messages
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
People
(Reporter: xenite, Assigned: sspitzer)
Details
Attachments
(3 files)
Mozilla build: 20020214 After Mozilla has downloaded new messages from a newsgroup (or sorted in new messages in a folder used for a mailinglist) the threading no longer makes any sense. After changing the threaded-view from ascending to descending and then back to ascending the messages are threaded the way they are supposed to be. Mozilla is configured only to display unread usenet-messages. steps to reproduce: 1. subscribe to a newsgroup, set the sort-mode to threaded and make sure that there are unread messages in that newsgroup folder. 2. re-connect to the newsserver and when there are new messages in that newsgroup folder open the folder. 3. click the threaded symbol twice to fix the wrong display.
Comment 1•23 years ago
|
||
screenshot please?
Reporter | ||
Comment 2•23 years ago
|
||
I blanked the names of the newsgroup participants since this newsgroup is only available on my ISP's newsserver.
Reporter | ||
Comment 3•23 years ago
|
||
I blanked the names of the newsgroup participants since this newsgroup is only available on my ISP's newsserver.
Comment 4•23 years ago
|
||
I've added another screenshot, that shows another threading error, that is very obvious. The new messages are placed at the bottom of the already expanded thread. Closing and opening the thread (eg clicking the triangle) resorts the thread, and works as a work-around.
Comment 5•23 years ago
|
||
confirming this behaviour in nightly 2002050108 win2k.
Comment 6•22 years ago
|
||
What about to download newer builds? 20020214 and 2002050108 sound quite old to me. :)
Comment 7•22 years ago
|
||
Still seeing this, only while reading a thread, posting myself and getting new messages, this is with 2002081119. Confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 8•22 years ago
|
||
Most likely this is a dupe of bug 93426. Reporter, I don't fully understand your description, please check if this is true. pi
Comment 9•22 years ago
|
||
It's the same :) Though I'm not the reporter, Steffen if you think I'm wrong, please re-open the bug. *** This bug has been marked as a duplicate of 93426 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•