Open
Bug 80936
Opened 23 years ago
Updated 3 months ago
Descending/Ascending order not remembered cross sorts
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: BenB, Unassigned)
References
Details
Reproduction: 1. Sort for Date, descending (i.e. latest first) by clicking on the Date clounm header twice. 2. Sort for subject (currently , even threading reproduces it, which makes it worse) by clicking on the subject colunm header once. 3. Sort for date again by clicking on the date colunm header once. Expected result: Sorted after Date, Descending order. Actual result: Sorted after Date, Ascending order. Rationale: You may tell me "Just click Date twice!". But in my opinion, sorting date descending is The Right Way for the inbox, and I told this Mozilla already. When I, after temporarily sorting after some other criteria, want to get back to my normal view, I just click on the column header (once) and expect everything to be "right" again.
Comment 1•23 years ago
|
||
It's not just the 'ascending, descending' bit. The 'sort by date, subject' etc does not persist too Irritating. I like to use sort by received since everyone has different time zones.
Comment 2•22 years ago
|
||
I don't ever expect to see descending order a default. Chronology is 1 before 2, a before b, older before newer, parent before child. Forget that the M$ way defaults to doing everything backwards, like putting the quoted original message on the bottom of the new message. If natural chronological order is not to be the default, then the order must be easily configurable. That said, I think ben is right. If sort time descending was last time sort prior to sorting on a different field, then when time is again selected for sort, descending should not require a second mouse click on the date heading.
Reporter | ||
Comment 3•22 years ago
|
||
> I like to use sort by received since everyone has different time zones.
If the sender's machine is properly configured, the time shown and sorted will
be translated into your local timezone.
This bug is even worse, if you prefer Order Recieved, because you can't sort
afetr that by the column headers and have to trigger *2* deep menu items to get
back to the "normal" view. Annoying.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: sspitzer → mail
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: laurel → message-display
Comment 4•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 5•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 6•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 7•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 8•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 9•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 10•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Reporter | ||
Updated•15 years ago
|
Status: UNCONFIRMED → NEW
Component: MailNews: Message Display → Message Compose Window
Product: SeaMonkey → Thunderbird
QA Contact: message-display → message-compose
Comment 11•15 years ago
|
||
This should probably stay with seamonkey. I believe one already exists for thunderbird - summary is multi sort or something like that
Comment 12•15 years ago
|
||
Wherever it belongs, it certainly doesn't belong in a Compose component.
Comment 15•13 years ago
|
||
Wow....this bug has been open for a DECADE! Is it ever going to get fixed?
Updated•8 years ago
|
Component: Message Compose Window → Folder and Message Lists
Updated•2 years ago
|
Severity: normal → S3
Comment 18•3 months ago
|
||
Sort by ascending/descending does not hold. Sort by Threaded/Unthreaded does not hold. Very annoying!
You need to log in
before you can comment on or make changes to this bug.
Description
•