316944 - Weird Grouped By Sort behavior when receiving new e-mail

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[Cyriel van 't End]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: 

I've installed Thunderbird 1.5 RC1 yesterday and everything looked just right before receiving new e-mail this morning. After I received new e-mail it looks like the Messages view doesn't update correctly (the mail i received yesterday doesn't have the 'Yesterday' header anymore but has been replaced by the details of the e-mail i received yesterday!). When I change views however (e.g. switch to another mail folder) everything looks fine again.

Reproducible: Always

Steps to Reproduce:
1. Make sure you didn't receive any e-mail until yesterday
2. Make sure you have navigated to the place where some new email is stored (usually Inbox, except when you have applied all kinds of rules)
3. Make sure this location has been sorted using "Group By Sort"
4. Fetch new e-mail using the "Get Mail" button
5. Take a look at the Messages view
6. Navigate to another item in the Navigation tree
7. Navigate back to the item you came from within the Navigation tree
8. Take a look at the Messages view again

Actual Results:  
The "Yesterday" header has been mysteriously replaced by the message details of the  e-mail message I received yesterday

Expected Results:  
Keep the "Yesterday" header shown

Comment 1

[Cyriel van 't End]

Attachment: This screenshot shows the weird behavior in action

Comment 2

[Cyriel van 't End]

Apparently this only behavior shows up only when receiving one new e-mail. If I receive multiple emails the Messages view behaves like it should.

Comment 3

[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 2.0.0.16)

Comment 4

[Cyriel van 't End]

It looks like this particular issue doesn't show up in the 2.x branch (at least not in the 2.0.0.16 version I'm using).

Marked as fixed.

Comment 5

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

-> WFM. Fixed is used for bugs with known patches.
https://bugzilla.mozilla.org/page.cgi?id=fields.html#resolution

Comment 6

[Cyriel van 't End]

Crap, thanks Gary. Think it's time for some coffee... :)