328708 - Some mails are opened after opening next one

Status: RESOLVED INCOMPLETE

(Thunderbird :: Mail Window Front End, defect)

Description

[vl.vl]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

Mail massages from one person are not open. They are opened after opening another mail message. Example:

Messege from the person -> No mail opened
Another mail from another person -> Open messege from the person (PREVIOSLY opened message)
Yet anoher message from (yet) another person -> Opens Message which has to be opened PREVIOUSLY.
etc.

When I reply with "quoting original massage" then no original message is quoting.
The messages from the person I can not save. The person uses ThunderBirds (0.9, 1.0.7, 1.5) all with the same result.

This problem is in SeaMonkey 1.0 and Thunderbird 1.5. Thunderbird 1.0.7 is OK.

Reproducible: Always

Steps to Reproduce:
1. Open message (-> empty window)
2. Open another massage from another person (in window is message from point 1)
3. Open yet onother message from another person (in window is message from point 2)
etc.
Actual Results:  
1. Open message (-> empty window)
2. Open another massage from another person (in window is message from point 1)
3. Open yet another message from another person (in window is message from point 1)
etc.

Expected Results:  
1. Open message (-> open message)
2. Open another message from another person (-> Open another message from another person)
3. Open yet another message from another person (-> Open yet another message from another person)

I have saved the problem message, but personal info is there. I will send it only for request and declaration to not use the info in improper way.

Comment 1

[vl.vl]

New finding:
The bug is not connected with the person. It is general problem of all messages. 

Comment 2

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is now 2.0.0.16)

Comment 3

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to previous comment. If you feel this change was made in error, please respond to the bug with your reasons why.