270726 - Attempting to rename folder causes erratic behavior

Status: VERIFIED DUPLICATE of bug 92165

(Thunderbird :: Mail Window Front End, defect)

Description

[Eric Hanson]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When attempting to rename folder, the pop-up window will come up, but after
capitalizing first letter (e.g. "test" to "Test"), clicking the "Ok" button will
do nothing.  

Also noticed that if this is attempted, and then click "Cancel" the rename
folder dialog will disapper, but will be unable to select folders in the current
mailbox, and clicking on another mailbox, cannot select messages withen.

Reproducible: Always
Steps to Reproduce:
1.  File -> new folder (name "test")
2.  Click on "test" folder and choose 'rename' from droplist
3.  In popup dialog, capitalize first letter
4.  Click Ok 

Actual Results:  
Mail currently in folder will disappear, dialog will remain on screen.

Expected Results:  
Renamed folder an continue to work as normal.

No themes, consistantly occurs using different methods of renaming (e.g. alt
click to rename)

Comment 1

[WADA:World Anti-bad-Duping Agency]

Has relation to Mozilla mail&news Bug 92165?

Comment 2

[WADA:World Anti-bad-Duping Agency]

See also Bug 234401 which blocks Bug 92165.
Are there any error on JavaScript Console?

Comment 3

[Mike Christie]

Also occurs on XP with slightly different symptoms.  If you try to change a
server-side folder name by changing only the capitalization, you get the
following error message:

The current command did not succeed.  The mail server responded: An object by
the same name was found..

The workaround is easy: add a character to the file name and save that change;
then change back to the original name, this time using the desired
capitalization.  Hence this is low priority.

Comment 4

[David :Bienvenu]

the last comment is really describing an imap server issue.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 7

[Mike Christie]

Still a bug in 1.0.7.  If the issue is that the IMAP server cannot handle the
request in this way, then I think Thunderbird should not send it a request that
cannot be handled.

I would like to reopen this bug, but there is no option to do so -- the only
radio button I am presented with says "Leave as RESOLVED EXPIRED".

Comment 8

[Ray Booysen]

Mike,

Reopening the bug for you.  Could you please test this behaviour on a newer
build than 1.0.7 to confirm?

Thanks

Comment 9

[Mike Christie]

This is confirmed as still a problem on 1.5 beta 2.

Comment 10

[Spencer B]

Still a problem in 1.5 (20051201).
Changing the first letter of the folder seems to trigger this bug, as indicated, but modifying the following characters in the name does not always trigger the bug.
RSS folders seem to respond a bit differently. In order to trigger the rename bug you must add a new subscription to that folder before renaming it.

Comment 11

[tom]

On Mac 10.5.1 When I rename a folder the immediate email contents of that folder remain ok but ALL THE CONTENTS OF ANY SUBFOLDERS, in that renamed folder, are LOST.  Problems similar to this have happend in older verstions also and on my old XP machine. Help!!!

Comment 12

[Nikola]

This bug persists on Vista too, in Thunderbird 2.0.0.12
There is an error in ErrorConsole:

Error: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIRDFService.GetResource]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: chrome://messenger/content/msgMail3PaneWindow.js :: SelectFolder :: line 1686"  data: no]
Source File: chrome://messenger/content/msgMail3PaneWindow.js
Line: 1686

Comment 13

[Wayne Mery (:wsmwk)]

I think we can just defer here to bug 234401 and Bug 92165, and close(dup) this bug.  Does anyone disagree?

I don't see the "dialog stays on screen" behavior using current trunk build.
I think reporter is gone (email fails).

Comment 15

[Serge Gautherie (:sgautherie)]

(In reply to Eric Hanson from comment #0)
> When attempting to rename folder, the pop-up window will come up, but after
> capitalizing first letter (e.g. "test" to "Test"), clicking the "Ok" button
> will
> do nothing.  

This (part) is bug 92165 actually.


(In reply to David :Bienvenu from comment #4)
> the last comment is really describing an imap server issue.

Comment 3 issue may (have) be a separate bug (to be filed)...


(In reply to Spencer B from comment #10)
> RSS folders seem to respond a bit differently. In order to trigger the
> rename bug you must add a new subscription to that folder before renaming it.

RSS case may (not (have)) be a separate bug (to be filed)...


(In reply to Nikola from comment #12)
> Error: [Exception... "Component returned failure code: 0x80070057
> (NS_ERROR_ILLEGAL_VALUE) [nsIRDFService.GetResource]"  nsresult: "0x80070057
> (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
> chrome://messenger/content/msgMail3PaneWindow.js :: SelectFolder :: line
> 1686"  data: no]
> Source File: chrome://messenger/content/msgMail3PaneWindow.js
> Line: 1686

This exception looks like (fixed per) bug 234401 comment 2.