User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20080404 Firefox/18.104.22.168 Build Identifier: Thunderbird/ version 22.214.171.124 (20080421) Tried to rename a folder in my inbox. RIght-slicked, tried to rename, then clicked OK-- and the screen behind the pop-up window cleared all e-mail in the folder from view and the opo-up screen that asked what name it should change to stayed on top and would not clear. After I hit 'Cancel'- the pop-up went away and the folder stayed the same name. Reproducible: Always Steps to Reproduce: 1. Right-Click on Existing folder 2. Rename from "Old Name" to "New Name" 3. Note that Renaming Box won't go away and you can't rename the folder 4. Hit Cancel. Actual Results: My folder was still named "Old Name" Expected Results: I wanted the folder to be named "New Name" No crash
(Q1) POP3(or "Local Folders")? Or IMAP? (Q2) Usual mail folder? Or Saved search folder(virtual folder)? (Q3) What is exact string of the "Old Name" and "New Name"? Special character such as /,#,?,:,... is used in the folder names? (Q4) Rename to very simple/short name such as "A" never work too? (Q5) Problem occurs even after restart of Thunderbird too? (Q6) Problem occurs even after restart of Thunderbird with safe mode too?
Hello, I can reproduce the issue but I have another hint regarding the bug: For me the error only appears when I try to rename an existing folder to upper-case characters only => e.g. the (local) folder name "testTEST" to "TESTTEST". HTH, Andreas
(In reply to comment #2) > the (local) folder name "testTEST" to "TESTTEST". Your case is Bug 92165(local mail folder) / Bug 104525(IMAP) Please not that bug summary says "Rename to a Completely Different Name".
WFM here on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090625 Lightning/1.0pre Shredder/3.0b3pre ID:20090625031837 but because not have response to comment #1 since June 2008 -> incomplete.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.