Closed Bug 199619 Opened 21 years ago Closed 21 years ago

Cannot create new bookmark folders in "Manage Bookmarks"

Categories

(SeaMonkey :: Bookmarks & History, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: u63580, Assigned: janv)

References

Details

(Keywords: regression, Whiteboard: [adt1])

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030326
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030326

Using Manage Bookmarks to attempt to create new bookmark folders.  Clicking the
"new folder" button, or selecting "new > folder" from the menu does not create a
new folder.  Nothing happens.

Reproducible: Always

Steps to Reproduce:
1. Manage bookmarks
2. New Folder
Actual Results:  
Nothing

Expected Results:  
New folder created

Running on RedHat Linux 8.0 (kernel 2.4.18)
Confirming with 3/27-04 build under XP.  (If somebody on MacOS also confirms, we
can make this ALL/ALL.)

However, there is a workaround.

More detailed explanation of what does NOT work:

1. When going into Bookmark Manager, do not ever try creating a new folder while
the "root" folder is highlighted - if you do, you'll never get a new folder
created in that BM session.

2. Do not use the New Folder button from the menu as your *first* method of
creating a new folder.  If you do, same deal as above.

To create a new folder, highlight one of the existing folders (not root) and use
the context menu (right-click).  Once you've done that, you can create as many
new folders as you wish.  Once you've created one via the context menus, the New
Folder button WILL work from that point on.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Glad to hear there is a way around it
Update: I just installed the 3/28-04 build, and can now use the New Bookmark
button again without having to resort first using the context menu.

However, the first problem in comment 1 remains - if I leave the root folder
highlighted and attempt to create a new folder (using any method) that function
is then horked for the remaining life of the BM session.
Flags: blocking1.4a+
I might be able to get a fix for this today, but don't hold your breath. Jan,
this is yours, I think...

From a debug build, got the following log:

###!!! ASSERTION: illegal value: 'aIndex >= 1', file
../../../../mozilla/rdf/base/src/nsRDFContainer.cpp, line 312
Break: at file ../../../../mozilla/rdf/base/src/nsRDFContainer.cpp, line 312
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsIRDFContainer.InsertElementAt]"  nsresult:
"0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
chrome://communicator/content/bookmarks/bookmarks.js :: anonymous :: line 1614"
 data: no]
************************************************************
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsITransactionManager.doTransaction]"  nsresult:
"0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
chrome://communicator/content/bookmarks/bookmarks.js :: anonymous :: line 1348"
 data: no]
************************************************************
An error occurred executing the cmd_bm_newfolder command
Assignee: ben → varga
Confirming this issue under 2003-03-28-08 Macho OS X build.
Severity: normal → major
Keywords: nsbeta1
OS: Linux → All
Hardware: PC → All
Verified Moz 2003032808/WXP SP1
Nav triage team: nsbeta1+/adt1
Keywords: nsbeta1nsbeta1+
Whiteboard: [adt1]
OK, in my impression the UI is broken... and this causes this error.

When you click "Create Folder" a folder is currently created on the same level
as the selected folder. Instead, I believe that it should be created *inside*
the current folder. The error here is caused because we're trying to create a
folder on the same level as NC:BookmarksRoot...bad.

This would involve reworking the logic at 
http://lxr.mozilla.org/seamonkey/source/xpfe/components/bookmarks/resources/bookmarks.js#613
and/or
http://lxr.mozilla.org/seamonkey/source/xpfe/components/bookmarks/resources/bookmarks.js#1333
Attached patch patchSplinter Review
Ok, so I disabled all commands for top root container and selected second row
in the view by default.
Attachment #118955 - Flags: superreview?(jaggernaut)
Attachment #118955 - Flags: review?(chanial)
Comment on attachment 118955 [details] [diff] [review]
patch

That's not the proper fix, because one should be able to paste on the bookmarks
root folder and if one selects it, he/she should be able to create a new
folder. Anyway, it's fine with me for 1.4a. Jan, please file a followup bug on
me for 1.4b.
Attachment #118955 - Flags: review?(chanial) → review+
Comment on attachment 118955 [details] [diff] [review]
patch

sr=jag. Add some comment to the change in bookmarks.js and maybe just comment
out (with a note why) the change in bookmarksTree.xml.

Please find a better fix for 1.4b
Attachment #118955 - Flags: superreview?(jaggernaut) → superreview+
Comment on attachment 118955 [details] [diff] [review]
patch

a=asa (on behalf of drivers) for checkin to 1.4a.
Attachment #118955 - Flags: approval1.4a+
Yes, this is only a quick fix, but as Benjamin pointed out the logic should be
changed. New folders should be created inside the current folder in general, not
only for the root container. Bug 200067 filed.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
This should be probably fixed in Phoenix too.
*** Bug 200649 has been marked as a duplicate of this bug. ***
Verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: