Closed Bug 210031 Opened 23 years ago Closed 23 years ago

messages in open threads are not get rearranged into the appropriate places after GetNewMessages

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 93426

People

(Reporter: AArzamasov, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 When using the news reader and having one or more threads opened, pressing GetNewMessages leads to messages fetching but its aren't go in the right place. e.g. if I have One Message (M1) and two replies (R1, R2) and R1-1 is a reply to R1 opened in a thread it looks like follows: M1 |-R1 | |-R1-1 | |-R2 Now, if I press GetNewMessages and new reply to R1 appears, it unfortunately will be placed under the R2: M1 |-R1 | |-R1-1 | |-R2 |-R1-2 Because of the whole thread did not get repainted. I beleive that this behaviour appears only on very high-traffic newsgroups where the replies are posted during the time I read the existing messages, but it very confusing. P.S. This is also applies to Mozilla 1.3 branch. Reproducible: Always Steps to Reproduce: 1. Open a thead with severals replies to one message 2. Post a reply to one One-The-Top Message from another window 3. In the first window having the thread opened press GetNewMessages and check out the reply goes into the wrong place Actual Results: Messages in the thread are not arranged in the right way Expected Results: I guess thread repainting after inserting new messages will help to get rid of this.
Looks like bug 93426. Arzamasov Alexey, if you agree, please mark this bug as a duplicate of that one.
*** This bug has been marked as a duplicate of 93426 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v dupe
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.