Closed Bug 310578 Opened 19 years ago Closed 12 years ago

NEW_BOOKMARK_FOLDER selected is not indicated in bookmarks manager view menu

Categories

(SeaMonkey :: Bookmarks & History, defect)

1.7 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mrmazda, Unassigned)

Details

(Keywords: dataloss, Whiteboard: [2012 Fall Equinox])

Tested on OS/2 with trunk and 1.7.12 and Linux with trunk.

To reproduce:
1-open bookmarks manager
2-open view menu
3-select some folder other than the root
4-open view menu
5-select the folder selected in 3 above
6-open view menu

Actual result:
no checkmark in front of "Set as New Bookmark Folder", or any other indication
that the selected folder is in fact the default folder for new bookmarks

Expected result:
checkmark in front of "Set as New Bookmark Folder" to indicate selected folder
has been set to be the default location for new bookmarks; or, "Set as New
Bookmark Folder" is not selectable as is the case with "Set as Personal Toolbar
Folder" when it has already been selected

Comments:
The problem is user confusion after having accidentally having set some folder
other than root as the default, and then not being able to find any new
bookmarks, thinking instead that no new bookmark(s) have in fact been added. Not
having some indication that the folder has been set is inconsistent with view
menu treatment of the personal toolbar folder selection.

This has the appearance of dataloss to any user with many bookmarks, so marking
keyword.
Comment 0 has incorrect reproduction steps. Substitute the following:
1-open bookmarks manager
2-select some folder other than the root
3-open view menu
4-select "Set as New Bookmark Folder"
5-open view menu
Reassigning as per Bug #32644
Assignee: p_ch → nobody
Version: unspecified → 1.7 Branch
Ability to "Set as New Bookmark Folder" is not available anymore thus making this report obsolete, so closing
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Whiteboard: [2012 Fall Equinox]
You need to log in before you can comment on or make changes to this bug.