77879 - can't add new folder

Status: VERIFIED DUPLICATE of bug 68539

(SeaMonkey :: Bookmarks & History, defect)

Description

[Brent Hendricks]

I am unable to add new bookmark folders in the bookmark manager.  The new folder
appears, but it won't let me rename it.  Then it does not persist after closing
the bookmark manager.

I don't know if it is related, but when trying to add the new folder, the
following gets output on the console

************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[Exception... "Component does not have requested interface" 
code: "-2147467262" nsresult: "0x80004002 (NS_NOINTERFACE)"  location:
"chrome://global/content/xulBindings.xml#textbox.select() Line: 1"]
[nsIController::doCommand]"  nsresult: "0x8057001c
(NS_ERROR_XPC_JS_THREW_JS_OBJECT)"  location: "JS frame ::
chrome://global/content/globalOverlay.js :: goDoCommand :: line 70"  data: no]
************************************************************
An error occurred executing the cmd_newfolder command

Comment 1

[Fabian Guisset]

Could you please tell us what build you are using? Thanks!
Steps that work for me using latest nightly (0.9) :
1) Open Manage Bookmarks window
2) Hit "New Folder" button
3) Enter a new name
4) Hit Enter
Here comes a new folder.

Comment 2

[Brent Hendricks]

Attachment: Long bookmarks file

Comment 3

[Brent Hendricks]

I'm using build 2001042703 from the trunk.

After poking around a bit more, it looks like the problem might only occur if
the bookmark list is long enough that the new folder is created "offscreen"

I can reproduce it consistently using the following steps:
1) Replace your bookmarks.html file with the one I attached
2) Run mozilla
3) Launch bookmark manager
4) Expand Folder
5) Select Folder
6) Click "New Folder" button
7) Enter new name
8) Hit enter

Comment 4

[Boris Zbarsky [:bzbarsky]]

Possibly related to bug 68539.

Bug 68539 claims that bug 68537 is not fixed.  Is that what you're seeing, Brent?

Comment 5

[Brent Hendricks]

yes, I think this is the same as 68539 (and I would agree that 68537 is *not* fixed)

Comment 6

[Boris Zbarsky [:bzbarsky]]

resolving duplicate

*** This bug has been marked as a duplicate of 68539 ***

Comment 7

[Fabian Guisset]

VERIFIED dup. I still don't understand why Boris and I are not seeing this.