Closed Bug 271179 Opened 20 years ago Closed 18 years ago

Grouped by Sort does not honor sort direction

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 267754

People

(Reporter: dm, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I normally sort messages so that the most recent appear at the top (by date
descending). When I select Grouped By Sort the sort returns to Ascending and the
Icon in the title line changes. The menu option still shows descending. I would
rather that whatever option I had chosen remains and the messages within the
group appear accordingly.


Reproducible: Always
Steps to Reproduce:
1. select sort by date, descending
2. select View, Sort By, Grouped by Sort
3. check it out

Actual Results:  
messages within the groups (eg Today) will appear in ascending order ie newest
at the bottom.

Expected Results:  
retained selected sort within the group ie newest messages at the top
Actually the sort order inside each group is the reverse of the original sort
order of all the messages. e.g. if you originally had the newest messages at the
bottom of the list, the newest messages are now at the top of the list in each
group.
(In reply to comment #1)
> Actually the sort order inside each group is the reverse of the original sort
> order of all the messages. e.g. if you originally had the newest messages at the
> bottom of the list, the newest messages are now at the top of the list in each
> group.

Whoops, I was wrong, it does always show the newest messages at the bottom.

*** This bug has been marked as a duplicate of 263678 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Duping this to the bug that actually had the fix for the problem -- but note that the fix regressed sometime, as 1.5.0.5 and 2a1/3a1 builds exhibit the problem.  See bug 340307.

*** This bug has been marked as a duplicate of 267754 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.