Closed
Bug 380445
Opened 18 years ago
Closed 15 years ago
Folder pane does not get updated when moving an IMAP folder into another IMAP folder
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: base12, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a5pre) Gecko/20070511 SeaMonkey/1.5a Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a5pre) Gecko/20070511 SeaMonkey/1.5a
If I try to move an IMAP folder into another IMAP folder, such as deleting a folder to Trash or just dragging any folder into another folder, the folder pane does not get updated, so as to appear that no move actually took place. However, if you collapse the account folder and then expand it, the moved folders show up in the correct new location.
Reproducible: Always
Steps to Reproduce:
1.Create a new folder in an IMAP account.
2.Drag the folder into another folder.
3.
Actual Results:
Nothing appears to happen, until you collapse the account folder and expand it again, at which time the folder pane will show the folders in their expected locations.
Expected Results:
The folder pane should update to show the new location of a moved folder without having to collapsed and expanded the account folder.
Could this be related to bug 117664 ?
Yes, still happening.
Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9pre) Gecko/2008043001 SeaMonkey/2.0a1pre
Our IMAP server is Sendmail.
|
||
Comment 3•16 years ago
|
||
I suspect this maybe fixed in tomorrow's nightly builds, if it's still happening for you.
I've tried it in SM 2.0.5pre and can no longer reproduce the bug. New folders appear as soon as created, and when moved by dragging, they appear immediately in the new location. Deleted folders appear immediately in the Trash folder.
I close this for now as wfm, see Comment 5 .
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
QA Contact: message-display
Resolution: --- → WORKSFORME
Version: Trunk → SeaMonkey 2.0 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•