Closed
Bug 115537
Opened 23 years ago
Closed 23 years ago
Inbox shows up alphabetically in folder list
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 115071
People
(Reporter: andrew.treloar, Assigned: sspitzer)
Details
When using nightly builds later than December 10, 2001, the Inbox folder is
listed in the folder list alphabetically, rather than at the top of the folder
list. This is both when subscribing to the folder and when using the mail client.
Confirmed using Fizizlla/2001121405, but the folder name order doesn't seem quite
alphabetical.
For example, I see, "Trash," "Drafts," "INBOX," "Jobs," "Mac," etc., which is certainly not
alphabetical. I can't determine any logic behind such an ordering.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•23 years ago
|
||
it depends on the default you set.. its not suppose to necessarily be at the top
of the list..
Greg,
you see a different issue, where the folders for imap/pop3/news or even local
folders are listed in order of subscription or in order the server is listed in.
mozilla doesn't currently alphabatize them.
Reporter | ||
Comment 3•23 years ago
|
||
Neither of the two above comments really relate to what I reported. Let
me try to explain it a bit better.
In Netscape 4.X and Mozilla (until recently!), the order of the folders for my
IMAP server was:
o Inbox
o Sent (because I keep sent mail on the server)
o Trash
then all the other folders in alpha order.
What I am commenting on is that with the recent nightly builds, the Inbox
no longer appears at the top but is sorted with the folders that start with I.
It has never worked like this before and is quite off-putting.
This one appears to be the same as bug 115071
Comment 5•23 years ago
|
||
It does look the same, so I'm marking as a dup.
*** This bug has been marked as a duplicate of 115071 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•