Closed
Bug 104812
Opened 24 years ago
Closed 16 years ago
IMAP folders not sorted the same way in Subscribe window as in Folder pane
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
EXPIRED
mozilla1.0.1
People
(Reporter: bugzilla, Unassigned)
Details
Attachments
(1 file)
The folders seems to unsorted in the Subscribe window. It oculd be really really
nice if they where sorted the same way as in the folder pane. See attached
screenshot
| Reporter | ||
Comment 1•24 years ago
|
||
*** This bug has been marked as a duplicate of 95920 ***
Status: NEW → RESOLVED
Closed: 24 years ago
OS: Windows 2000 → All
Hardware: PC → All
Resolution: --- → DUPLICATE
Summary: IMAP folders not sorted the same why in Subscribe window as in Folder pane → IMAP folders not sorted the same way in Subscribe window as in Folder pane
Bah. Here's to me, trying to wake up. Accounts!=Folders
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•24 years ago
|
Target Milestone: --- → mozilla1.0.1
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 4•21 years ago
|
||
This seems to be part of bug 98570 (see last paragraph in parantheses there).
Updated•21 years ago
|
Assignee: sspitzer → mail
Status: REOPENED → NEW
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: stephend → search
Comment 5•17 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
Updated•17 years ago
|
Assignee: mail → nobody
QA Contact: search → message-display
Comment 6•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 16 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•