111074 - Show Alert dlg when renaming a folder during summary file building

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Sheela Ravindran]

Commercial build:  2001-11-19-06 linux rh 6.2, mac os x 

I saw this when verifying bug 105108 which is renaming a local folder while its 
is being reparsed causes crash.  In this bug we are supposed to show a dlg which 
alerts the user" The folder could not be renamed. Perhaps the folder is being 
reparsed, or the new name is not a valid name" OK
I see this come up only on windows and not on other two platforms.

Steps to reproduce: 
Delete .msf file of a local or pop folder
start application
Click on the folder
When it starts building the summary file
Rename the folder

Actual: It should show the alert dlg as mentioned above. When you click OK the 
summary file stops building and clicking again on the folder should start 
rebuilding the summary file

Expected: Stops building the summary file but does not show the dlg

This behavior needs to be consistent on all three platforms.

Comment 1

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 2

[Robert Kaiser]

MASS-CHANGE:
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

Comment 3

[Robert Kaiser]

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