Closed Bug 327763 Opened 19 years ago Closed 17 years ago

POP inbox re-sorts itself by Subject on refresh (rather than by date).

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 366665

People

(Reporter: jdfrost, Assigned: mscott)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: version 1.5 (20051201) I set the POP inbox sort to sort by date, but it resets to sort by Subject (ascending) every time navigate to a different folder, and the I return to the inbox. This consistently occurs, but only in one of my several local Tbird POP folders on my WinXP Pro computer. All my POP inboxes are stored in the default local folders location, which is compressed every so often. The other POP inbox doesn't have this problem (it remembers to sort by Date when refreshed). Reproducible: Always Steps to Reproduce: 1. Open 3-pane view of the POP Inbox. 2. Click on the Date column header to sort it (either asc. or desc). The message headers sort as expected. 3. Browse to a different folder. 4. Return to the POP Inbox. The message headers now are sorted by Subject (ascending). Actual Results: The message headers in the inbox are sorted by ascending Subject, which is not the order in which I left them.... Expected Results: The message headers should appear sorted by Date (which was the order they were in when I left the folder). This occures in only one of the two POP Inboxes on my computer. The problem does not occur in my IMAP inbox. I have 21,000 messages in my inbox. All local files are stored in the default local folder. I compress it every few days. I am using the default TBird theme. The pc is running NAV 2005 and Microsoft AntiSpyware (latest versions of all).
Version: unspecified → 1.5
QA Contact: front-end
reporter, Joshua, seems to be gone. duping to bug 366665
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.