Closed Bug 30747 Opened 25 years ago Closed 21 years ago

Sort threads by date, newest first, is confusing

Categories

(MailNews Core :: Backend, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 20385
Future

People

(Reporter: rzach, Assigned: sspitzer)

Details

(Whiteboard: [nsbeta1+ 1/28])

If you have threaded view and sort by date with newest first, the messages
inside a thread are sorted by date, newest first, as well. This makes for a
confusing thread display, since later messages will appear below a message if
it's a reply and above if it's a reply to the thread leader.  Similar things
happen when you sort on another column.

I would expect threaded sort by date descending to work exactly like descending
thread view in NS 4.7, where the threads are displayed as usual, but sorted by
date of thread leader, newest first.  Alternatively, you could make the behavior
I requested in bug 20385, namely to sort threads by date of newest message.

Linux build 2000.03.06.09
Hey, Scott, do we have any control over this?
Assignee: bienvenu → putterman
we currently don't have control over this, but the goal is to make it so that 
only top level messages are sorted and that everything else is by order 
received.
QA Contact: lchiang → fenella
Status: NEW → ASSIGNED
Target Milestone: --- → M18
moving to future milestone.
Target Milestone: M18 → Future
nominating for mail3, and reassigning to sspitzer
Assignee: putterman → sspitzer
Status: ASSIGNED → NEW
Keywords: mail3
marking nsbeta1+ and moving to mozilla0.8.  
Keywords: nsbeta1
Priority: P3 → P2
Whiteboard: [nsbeta1+]
Target Milestone: Future → mozilla0.8
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9
Keywords: nsbeta1nsbeta1-
Whiteboard: [nsbeta1+] → [nsbeta1+ 1/28]
Target Milestone: mozilla0.9 → Future
marking nsbeta1-. We are going to focus on thread pane performance rather than this.
QA Contact: fenella → laurel
Bug 20385 mentioned in comment 0 is now fixed - is this still relevant? I don't
think so. I propose closing this bug as duplicate of bug 20385, because the
original bug description mentioned that as an acceptable way of solving the
problem and that has been done.
Blocks: 236849
No objections to my previous comment after 3 months => resolving.

*** This bug has been marked as a duplicate of 20385 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
No longer blocks: 236849
You need to log in before you can comment on or make changes to this bug.