RFE: sort Re: after main message when sorting by title

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
--
enhancement
RESOLVED EXPIRED
15 years ago
12 years ago

People

(Reporter: David Hagood, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
It seems that when you select "Sort by title" mode in the mail/news window, that
it does a simple alphabetical sort. As a result,

  Re: Zounds!

will sort BEFORE
  Zounds!

Which is a bit confusing. It would be nice if the sort algorithm were smart
enough to put Re: $string after $string in a sort.

Updated

15 years ago
QA Contact: olgam → laurel

Comment 1

15 years ago
Don't forget that you''l also see Fwd:, Aw:, Sv:, etc (bug 108163) ... so it's
not always that simple. Can't we just use date as in bug 72493 ?

Comment 2

15 years ago
Created attachment 120126 [details]
Screenshot of sorted-by-title with several Re:'d threads

Here's a screenshot of what I'm seeing currently, sorting by subject,
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030408

Note that the group on the bottom is sorted according to reporter's desire;
but there is another group in the middle which is sorted incorrectly.  I didn't

include the date field, but those three messages are sorted out of order for
date, too.  So maybe there's an actual bug there.

btw, bug 72493 has to do with sub-sorting within threads, different from this
bug's desire to flat-sort alphabetically by title, but be smart about the
prefix(es).  Sorting by date would be a logical secondary order, but that's
related to multi-sort, Bug 57898.
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.