Closed
Bug 111018
Opened 23 years ago
Closed 23 years ago
Lost IMAP folders after second launch from today trunk build
Categories
(MailNews Core :: Networking: IMAP, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: huang, Assigned: darin.moz)
Details
(Keywords: dataloss, platform-parity, smoketest)
Used 11-20-09-trunk build Lost IMAP folders after second launch from today build 1) Login to an IMAP mail account. 2) You will see there was bug 110938 3) But, after you relaunch again for the second time Actual Results: All the IMAP folder are disappear after the second launch, it only displays IMAP Inbox and Trash folders. Expected results: Should display all the existing IMAP folders which created before.
Reporter | ||
Comment 1•23 years ago
|
||
Nominating nsbeta1 and dataloss
Comment 2•23 years ago
|
||
Looks to me like this may be related to darin's check in to nsURLParsers.cpp last night. I backed that file out and I'm not having any problems with loss of imap folders.
Assignee: mscott → darin
Keywords: smoketest
Reporter | ||
Comment 3•23 years ago
|
||
Adding pp for the keywords since problem is not occurring on the Linux platform....
Keywords: pp
Reporter | ||
Updated•23 years ago
|
Summary: Lost IMAP folders after second launch from today build → Lost IMAP folders after second launch from today trunk build
Comment 4•23 years ago
|
||
again, feel free to backout, if your local tree is fixed, mscott.
Assignee | ||
Comment 5•23 years ago
|
||
i backed out revision 1.3 of nsURLParsers.cpp
Comment 6•23 years ago
|
||
Thanks Darin. I'm going to mark this fixed then to get it off the smoketest radar.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•23 years ago
|
||
Verified on 11-21-10-trunk build After removed Mozilla directory and created new profile, IMAP fodlers are displaying again......marking as verified.
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
•