Closed Bug 200813 Opened 23 years ago Closed 23 years ago

New Folder requires a double-click to exit dialog

Categories

(SeaMonkey :: Bookmarks & History, defect)

Product:
SeaMonkey
Component:
Bookmarks & History
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: Lil46john, Assigned: janv)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030402 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030402 Feature? Reproducible: Always Steps to Reproduce: 1. Go to Bookmark Manager 2. add New Folder 3. Rename it to something other than New Folder Actual Results: I have to click OK 2 times to exit the dialog Expected Results: 1 click to exit the dialog
.
Assignee: ben → varga
This should be fixed along with bug 200498. Please verify.
I don't think so. I just finished downloading 2003040604 Is it fixed in this build? Are you sure this is related to bug 200498?
No, I checked in a fix today, so it can't be in 2003040604 build. Please verify in JS console, if you get NS_ERROR_FILE_ALREADY_EXISTS, then it should be fixed by bug 200498. I'll try to veridy on Mac.
I don't see a 2003-04-07 build
I just updated my Mac build to the tip. I can't reproduce this bug anymore.
No, I checked in a fix today, so it can't be in 2003040604 build. Please verify in JS console, if you get NS_ERROR_FILE_ALREADY_EXISTS, then it should be fixed by bug 200498. I'll try to veridy on Mac. I don't see NS_ERROR_FILE_ALREADY_EXISTS Is there a way to reproduce it? The new build still has this problem.
Well, that build probably doesn't have the fix. Try another build when it appears
I just finished downloading phoenix 4-7-2003 It used to have this same Mozilla bug, but the new build doesn't have it, so I guess it's fixed
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
verified with 2003040808
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.