Closed Bug 317517 Opened 20 years ago Closed 20 years ago

can't create a new folder with the same name of other that have been deleted

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Version:
1.7 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: juan, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 I encountred this problem with the Mozilla Suite 1.7.12, but i think that this problem also affect the Thundherbird mail client. The problem is: if you create a folder with a name (any name, eg.: test) in the 'Local Folders', after then, delete it (test) you aren't able to create again a folder with that name (test). There's not difference if restart (or not) the Mozilla Suite. Using Windows XP SP2 - Brazilian Portuguese Reproducible: Always Steps to Reproduce: 1. Create a 'New Folder' in 'Local Folders' let's call 'test' (without quotes) 2. Delete the folder 'test' 3. Empty Trash 4. Restart Mozilla 5. Try to create a 'New Folder' in 'Local Folders' with the same name 'test'. The first time that you click the OK button, nothing happens, if you click it again, then a window saing 'A folder with that name already exists. Please enter a different name.'. Actual Results: after created a folder named 'test' (without quotes), deleted it, empty trash, restarted mozilla, then I tried to create again a folder with the same name os the other that i have deleted and erased from the trash, but i can't, "the folder with that name already exists" sad mozilla. Expected Results: create a new folder because, there's nothing other folder with the same name. I'm using the Modern Theme that came with mozilla
Version: unspecified → 1.7 Branch
what about a trunk seamonkey build? I believe I fixed this a long time ago - the fix just isn't on the 1.7.x branch.
(In reply to comment #1) > what about a trunk seamonkey build? I believe I fixed this a long time ago - > the fix just isn't on the 1.7.x branch. > Yes, in the seamonkey this problem don't occurrs. The mozilla suite will be now seamonkey?
yes, exactly.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.