187061 - New bookmark should be inserted before the selected bookmark/folder in Bookmark Manager

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, defect)

Description

[Michael Graubart]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.3b) Gecko/20021226
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.3b) Gecko/20021226

In Netscape 4.x, if one highlights a bookmark or folder in 'Edit Bookmarks' and
then enters a new bookmark or folder, the latter appears directly below the
highlighted item. This is very convenient, as (by choosing the desired position)
it saves searching and repositioning.
In Mozilla 1.3b, a new folder appears immediately above the highlighted item,
but a new bookmark appears at the bottom of the whole bookmarks page or at the
bottom of the list contained in whatever folder the highlighted item is contained. 
This is particularly inconvenient, because the failure of 'Find' to show where
in the Bookmarks page a bookmark is located has still not been rectified.

Reproducible: Always

Steps to Reproduce:
1. In 'Manage Bookmarks', highlight an item.
2. Choose 'New folder', enter details, click 'OK'.
3. Repeat process with 'New bookmark'.

Actual Results:  
At 2., the new folder appears immediately above the highlighted item.
At 3., the new bookmark appears at the bottom of the list or sub-list.

Expected Results:  
At 3., the new bookmark (like a new folder) should appear immediately above the
highlighted item.

Mac G3 (old beige). OS 9.2.2. Modern theme.

Comment 1

[Daniel Wang]

*** Bug 189967 has been marked as a duplicate of this bug. ***

Comment 2

[Daniel Wang]

confirming

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 7

[Michael Graubart]

This behaviour is still present in SM 2.0.5Pre, though I have got so accustomed to it that I might pssible not now report it as a bug.

I am now on Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1.10pre) Gecko/20100422 SeaMonkey/2.0.5pre

Comment 8

[Michael Graubart]

Sorry! 'pssible' in Comment 7 should read 'possibly'.