158650 - File Bookmark: Clicking "Use Default" selects default folder in tree but doesn't scroll to show it

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, defect)

Description

[Tuukka Tolvanen (sp3000)]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722
BuildID:    trunk cvs 2002-07-22

In the "Add Bookmark" dialog (Bookmarks > File Bookmark) dialog:
Clicking "Use Default" selects default folder in the bookmarks tree, which may
be scrolled out of sight.

The bookmarks tree view should be scrolled to display the selection.

Reproducible: Always
Steps to Reproduce:
1. Have some bookmark folders, set one as default (bookmarks > manage bookmarks:
select a folder, view > set as new bookmarks folder)
2. bookmarks > file bookmark
3. see to it that the default bookmerks folder is scrolled outside view
4. click on "Use Default"

Actual Results: Selects default folder, but that is not visible.

Expected Results: The bookmarks tree view should also be scrolled to display the
selection.

Comment 1

[Jason Bassford]

Also see related bug 158648.  I suggest that the default folder actually be
what's selected by default (which makes sense to me), and scrolled to the center
- so long as another issue is first addressed.

Comment 2

[Ben Goodger (use ben at mozilla dot org for email)]

Mass reassign of my non-Firefox bugs to [e-mail]

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 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