378576 - Row invalidation problems with Messages sorted or grouped by date when passing midnight

Status: RESOLVED FIXED

(Thunderbird :: Folder and Message Lists, defect)

Description

[Michael Letzgus]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Version 2.0.0.0 (20070326)

When Messages are sorted and groupd by date they are displayed in categories labeled "today", "yesterday", "last week"... - this is fine.

But when passing midnight these labels become strange:
The "today"-category is now labeld with the subject of the first mail retrieved after midnight!

Only restarting Thunderbird or selecting an other mail folder helps.


Reproducible: Sometimes

Steps to Reproduce:
1. Leave Thunderbird running with mails sorted and groupd by date
2. Watch your inbox and wait until midnight
3. Continue watching yout inbox an wait for incoming mail
Actual Results:  
Labels are screwed up: "<subject of first retrived mail>", "yesterday", "last week"...

Expected Results:  
Lables should be correct: "today", "yesterday", "last week"...

Comment 1

[Patrick]

Are you still seeing this in the Latest Trunk build?

Comment 2

[Thomas D. (:thomas8)]

This should be checked if still occuring after fix for bug 517467 will land
today

Comment 3

[Thomas D. (:thomas8)]

Unfortunately, we don't properly refresh the FolderView when midnight passes. The right data seems to be there, but message list display updates only those message rows that the user happens to hover over, resulting in chaos on the display. If the user doesn't hover over, we do nothing, and yesterday's messages are still shown as today's. Both bad.

Similar to  Bug 497643 -  With View > Grouped by Sort G enabled, clicking on date column header has row invalidation problems in message list, but this one happens without "Grouped by sort" and will thus occur much for frequently, i. e. every time when we pass midnight without the view being refreshed for some other reason.

Comment 4

[Hartmut Welpmann [:welpy-cw]]

This should now be fixed by bug 1520435.