695122 - valid subject displayed as blank in thread pane (preceded by bogus header)

Status: RESOLVED WORKSFORME

(Thunderbird :: Untriaged, defect)

Description

[SR]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build ID: 20110928134238

Steps to reproduce:

Look at #341568.

Comment 1

[:aceman]

Do you say this has appeared again? Please attach a sample message in EML format.

Taken the description from bug 341568:
SR 2006-06-15 00:06:54 CEST

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

Looking at the attached picture gives immediate understanding of what happens.

The subject displayed in the list of messages is not the same as the subject displayed in the message.

Reproducible: Didn't try

Steps to Reproduce:
First time it happened for me.
Actual Results:  
subjects are different.

Expected Results:  
The same subject should be displayed on the UI.

I've looked at other bugs, and there is only one subject.
I attache the mail as well.

Comment 2

[SR]

All the elements and details are in #341568 which I reported and is not to be closed in my opinion.

Comment 3

[Ludovic Hirlimann [:Usul]]

(In reply to SR from comment #2)
> All the elements and details are in #341568 which I reported and is not to
> be closed in my opinion.

It was fixed with a patch. If this came back , it's probably because something else broke it. Using http://www.rumblingedge.com/2009/02/24/howto-find-regression-windows-through-manual-binary-search/ can you try to figure out when it broke again ?

Comment 4

[Wayne Mery (:wsmwk)]

SR,
Do you still see this issue when using a newer version?

Comment 5

[SR]

Could not reproduce it with TB 45.3.0.
Method used :
 1- download the .eml file
 2- drag and drop it to an open TB, on the INBOX of an account.
Result :
The subject is correctly shown, as expected, in the list of messages.

Looks like it's been fixed. Very well.

Comment 6

[Wayne Mery (:wsmwk)]

Thanks very much for retesting it