Closed Bug 154853 Opened 22 years ago Closed 22 years ago

added bookmarks don't appear at the end of the menu

Categories

(Camino Graveyard :: Bookmarks, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: sfraser_bugs)

Details

i thought that this was erratic with older builds, but i can reproduce this with
2002.06.27.05 chimera bits.

1. hit cmd+D to add a bookmark (eg, while viewing the bugzilla query page).
2. edit the Name field in the Bookmark dlg (optional, really). hit OK.
3. pull down the Bookmarks menu

results: the added bookmark is not at the bottom of the menu (as would be
expected), but is instead 4th from the bottom.

4. repeat adding another bookmark, and look at the menu again.

results: again, the most recently added bookmark is 4th from the bottom (the
previously added one is 5th from the bottom).

interestingly, when looking at the bookmarks tab in the Sidebar, the order of
the bookmarks is fine --last ones at the bottom.
another interesting thing: after quitting and restarting, the order of the
bookmarks menu is "reset" --ie, it then looks fine (recently added items at the
bottom).
I know why this happens.
Assignee: saari → sfraser
note: if, while in the bookmarks dlg, i place the new bookmark in a folder, i
don't see this problem --ie, the new bm appears at the bottom of that folder's
submenu.
Yeah, this only affects the top-level menu. The new item is added N items too
high in the menu, where N is the number of 'permanent' items (above and
including the separator) in the menu.
Status: NEW → ASSIGNED
Blocks: 154286
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Verified with 07-01 build on OS 10.1.5.  Added two bookmarks and both were
placed at the bottom of the menu in order.  Also placed in the right order in
the sidebar.  Upon quitting and relaunching chimera, these two bookmarks are
still in the same right places.
Status: RESOLVED → VERIFIED
No longer blocks: 154286
You need to log in before you can comment on or make changes to this bug.