Closed
Bug 15142
Opened 25 years ago
Closed 24 years ago
Need to do secondary sort on thread pane
Categories
(MailNews Core :: Backend, defect, P2)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
FIXED
M18
People
(Reporter: phil, Assigned: nhottanscp)
References
Details
(Whiteboard: [nsbeta3+][nsbeta2-])
When I sort the thread pane by sender, the messages come out in random order,
within each sender. Secondary sort by date would be more desirable.
4.x sort of does this, since it presents messages in ID order, which is usually
date order (but sometimes not).
In some perfect world, it might even be nice to specify multiple sort keys, but
I'd be happy with secondary sort on date.
Reporter | ||
Updated•25 years ago
|
Target Milestone: M15
Reporter | ||
Comment 1•25 years ago
|
||
M15. rjc, do we need to extend RDF searching for this?
Comment 2•25 years ago
|
||
I'll check in some changes when the tree opens today [Nov 10] to enable this.
You'll just need add a [optional] "rdf:resource2" attribute [to accompany the
"rdf:resource" attribute] to relevant 'treecol' tag(s).
I'll add another comment on this bug when the check-in is complete.
Comment 3•25 years ago
|
||
Support for secondary sort keys is now checked in. Feel free to play with it.
Comment 4•25 years ago
|
||
great! thanks.
Comment 6•25 years ago
|
||
I'm still seeing the random list when sorting on sender with the 11/17/99 build.
Comment 7•25 years ago
|
||
that's because I haven't done anything to incoporate rjc's changes into mailnews
yet.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 8•25 years ago
|
||
I checked in the fix. When you sort by anything besides date, the secondary
sort is by date.
Linux Redhat 6.0 (2000-01-20-08 M13)
Win_nt 4.0 (2000-01-20-09 M13)
Mac (2000-01-20-08 M13)
Secondary sort by date is working in both POP and IMAP accounts on all
platforms.
Status: RESOLVED → VERIFIED
Comment 10•25 years ago
|
||
Reopening - for large folders, secondary sort works in chunks (incorrectly). For
example, if you sort on sender, you see messages from that sender organized as
follows:
12/17/99
1/1/00
1/4/00
7/31/99
8/15/99
1/10/00
2/1/00
6/15/99
10/31/99
Within a "chunk", the messages are sorted correctly by date, however, the sort
should occur across all of these chunks.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 11•25 years ago
|
||
reassigning to rjc. I'm pretty sure I'm setting the secondary sort key
correctly.
Assignee: putterman → rjc
Status: REOPENED → NEW
Comment 12•25 years ago
|
||
Sol, can you retest this? I'm not seeing this problem. Do you have have
threading on or off? Can you determine a threshhold size for which this is
exhibited, but below it isn't?
Assignee: rjc → sol
Comment 13•25 years ago
|
||
Rich: I'm still seeing this problem using the following builds on WinNT4:
2000-02-04-10
2000-02-06-08
I have threading turned *off*.
I sort by sender. If I have a lot of mail from the sender in the folder, then
the first 130 or so messages from that sender are correctly sorted by date.
After this first block of correctly sorted messages, another block of messages
from the same sender (again sorted by date within the 2nd block) is presented.
Let me know if you want to see this behavior on my machine.
Comment 14•25 years ago
|
||
As soon as I figure out who Rich is, I'll send him over. <grin>
Comment 15•25 years ago
|
||
Not sure how this bug got stuck to me, but please, get it off me!
Reassigning to putterman - not sure who the right owner is at this point.
Assignee: sol → putterman
Comment 16•25 years ago
|
||
I'm not sure why this is getting reassigned to me!
I figure Sol mixed up rhp with rjc. Reassigning back to rjc.
Assignee: putterman → rjc
Updated•25 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 17•25 years ago
|
||
This bug is driving me crazy. It makes sorting in the thread pane pretty much
useless. Can we pretty please have a fix for this soon?
Comment 18•25 years ago
|
||
Scott, I'm looking at "mozilla/mailnews/base/resources/content/threadPane.xul"
and I don't see any "rdf:resource2" (note the 2 for secondary!) attributes on
the <treecol> tags in this file.
[Are you sure that your change from 1/12/2000 went in? Or, am I looking at the
wrong file? Or, ... ?]
Assignee: rjc → putterman
Status: ASSIGNED → NEW
Comment 19•25 years ago
|
||
I'm pretty sure I set it programatically in commandglue.js in SortColumn.
Comment 20•25 years ago
|
||
Yeah, I see the JavaScript. (Any reason why, instead of just setting it in
XUL?) Continuing to look at it.
Assignee: putterman → rjc
Comment 21•25 years ago
|
||
Yeah, I was trying to make it so that if we ever had a ui to change the
secondary sort that we were set up for it.
Comment 22•25 years ago
|
||
I'm noticing that if I comment out TEST_SORT (line #96 in
mozilla/rdf/content/src/nsXULSortService.cpp) which reverts to older sorting
code, the problem seems a lot better.
Phil/Scott, if you comment that out and rebuild RDF, do you see this also?
Comment 23•25 years ago
|
||
that would be amusing. If that's the case, then I can take a look at it, though
if you see anything obviously wrong, I'd appreciate the help.
Assignee: rjc → putterman
Comment 24•25 years ago
|
||
ok. It was my fault. I accidentally typed node1 instead of node2 someplace and
that caused all of the problems. Changing it to node2 makes it work for me.
Comment 25•25 years ago
|
||
Great! :^)
Comment 26•25 years ago
|
||
fix was checked in yesterday.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 27•25 years ago
|
||
Linux (2000-04-11-09-M15)
Win32 (2000-04-11-09-M15)
Mac (2000-04-11-08-M15)
I have a folder that contains 2315 messages. The problem still exists in certain
block of senders. This occurs on all 3 platforms. Re-open the bug.
Status: RESOLVED → VERIFIED
Comment 28•25 years ago
|
||
When you reopen this bug, the target milestone should be set to a more
appropriate one.
Comment 29•25 years ago
|
||
Set it to M17 per Scott Putterman
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Target Milestone: M15 → M17
Comment 30•25 years ago
|
||
Mail Review recommends not in this release. Marking M20.
Target Milestone: M17 → M20
Comment 31•25 years ago
|
||
so, this is just a bug. for some reason it works fine in debug builds but not
in release builds. I'm not sure we should remove this from the product just
yet. We should spend some time on it. On the other hand, how much time do we
want to spend on this if it turns out that there's some sorting bug that only
manifests itself in the release build and might be hard to track down?
Reporter | ||
Comment 32•25 years ago
|
||
I'd invest a lot in it since it makes sorting by anything other than date look
wrong. Bummer that it's release-only. Are you going to move the target milestone?
Updated•25 years ago
|
Target Milestone: M20 → M17
Comment 33•25 years ago
|
||
I think we should nominate this.
Comment 34•25 years ago
|
||
This sure would be nice... but there are too many critical beta2 bugs. Putting
on beta2-, but nominating for beta3. As stated, this is a bug in the non-debug
build, which is a hassle, and often a time sink.
Keywords: nsbeta3
Whiteboard: [nsbeta2-]
Comment 35•25 years ago
|
||
+ per mail triage
Whiteboard: [nsbeta2-] → [nsbeta3+][nsbeta2-]
Target Milestone: M17 → M18
Comment 37•25 years ago
|
||
cc'ing nhotta.
I have a theory that this is a collation key problem. I have output for a
folder of mine where it's telling me that comparing Scott MacGregor to Scott
MacGregor is returning a sort order of 1 rather than a sort order of 0. The
collation keys appear to be different. The first one gets ...................a0
and the second gets ......................a. I only see the bug in release
mode. Any ideas on what is happening?
Comment 38•25 years ago
|
||
Don't know much about collation keys, but debugging, I'm seeing one Scott
MacGregor get "???????????h???aa" and another get "???????????h???aa ????a" Is
it possible some buffer's being reused and garbage is in it?
Assignee | ||
Comment 39•25 years ago
|
||
Scott, could you give me a simple data and I will investigate if this is a
collation key problem.
Comment 40•25 years ago
|
||
nhotta gave me a patch that makes this work on my release build.
Whiteboard: [nsbeta3+][nsbeta2-] → [nsbeta3+][nsbeta2-] HAVE FIX
Comment 41•25 years ago
|
||
I checked in the most recent patch Naoki sent to me.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 42•25 years ago
|
||
Reopening this seems to be happening on Linux and Mac still.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 43•25 years ago
|
||
Linux (2000-08-21-12 M18)
Win32 (2000-08-21-08 M18)
Mac (2000-08-21-08 M18)
This bug is still on Mac POP and IMAP
Linux in IMAP only, Not POP.
Win32 is OK.
Show it to Scott. M. He will re-open it.
Comment 44•25 years ago
|
||
Oh. I meant Scott P, not Scott M.
Comment 45•25 years ago
|
||
reassigning to nhotta. I'm pretty sure this is a collation key bug based on the
fact that Windows got fixed with this and if I remember correctly, this code is
different per platform. I'm pretty sure the fact that it's not working for
certain folder types is coincidental.
Assignee: putterman → nhotta
Status: REOPENED → NEW
Whiteboard: [nsbeta3+][nsbeta2-] HAVE FIX → [nsbeta3+][nsbeta2-]
Assignee | ||
Comment 46•24 years ago
|
||
Checked in a fix. I tested on my Macintosh release build and the sort problem
was fixed with this change.
Status: NEW → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
Comment 47•24 years ago
|
||
Mac (2000-09-08-20 M18)
Linux (2000-09-11-08 M18)
This problem is fixed.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•