77611 - Last used folder should be added to Manage Bookmarks toolbar

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, enhancement, P5)

Description

[André Langhorst]

There are two not to hard to implement (guessing) features, which could ease the
use of bookmark managing a lot.

1) enable the sidebar in [manage bookmarks], this way you can sort a large
amount of bookmarks easily - currently it isn't possible without hassle, in
addition to having the sidebar in this window you can sort your bookmarks with
drag'n'drop

2) enable [file bookmark] in right click menus in the personal toolbar as well
as in my sidebar

3) since [file bookmark] is available in a few places, it would be *very*
comfortable to have at least the *last* folder an user filed a bookmark in
remembered, I would suggest placing this directly below [file in [current
folder]] like
[file in [last foldername filed to]]

b) the enhanced version of this would display a history (like the [recent files]
in many applications) with about 10 (maybe configureable) folders the user last
filed to

Maybe this point does not apply to bookmarks directly as all components using
the [file to...] mechanism (eg. mail) would benefit, if anyone knows where to
move it, please copy&paste it out

4) the absolute ease would be if a generic item [last folder] would be added to
the toolbar in [manage bookmarks] or at any other better place, where you can
simply drag'n'drop your bookmarks on, no menues, no clicking, no waste of time

b) enhancement like 3b, create a new [history toolbar] where you can drag'n'drop
items directly on, that would be absolutely killer

Comment 1

[André Langhorst]

I don't understand why it can be so hard to add a sidebar to "manage bookmarks",
thus here a little workaround:

Enter this into your location bar...
chrome://communicator/content/bookmarks/bookmarks.xul
and there you are, on the left the sidebar with bookmarks and on the right bar
the manage bookmarks window. Perfect for sorting boomarks and even better for
migrating bookmarks from IE !!!

I suggest to add this as a link just until manage bookmarks has improved, this
should be done quickly (I guess) and the navigation bar should be hidden, so
that users do not see this chrome stuff.

Proposing mozilla1.0 for applying the "workaround".

Comment 2

[André Langhorst]

improvement: is it possible to define a XUL frameset? so that bookmarks.xul is
loaded into the left frame and and the browser (for displaying bookmarks) is in
the right frame? that would avoid unnecessary opened windows.

Comment 3

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

Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter 
email notifications caused by this by searching for 'ilikegoats'.

Comment 4

[Paul Chen]

Mass move Ben's bugs dumped on me marked future with p5 to get off my untriaged
radar. You can filter out this email by looking for "ironstomachaussie"

Comment 5

[Peter Trudelle]

mass reassign of pchen bookmark bugs to ben

Comment 6

[Chris Lyon]

André, you've described 4 seperate enhancements, some of which are duplicates 
of other logged bugs.  In the future, please limit yourself to 1 issue per bug 
report.

1) You're asking for the same functionality as bug 23214 
2) WFM 2002022208
3) Duplicate of bug 75452


Resummarizing based on issue 4 and changing severity.

Comment 7

[Robert Kaiser]

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 8

[Robert Kaiser]

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 9

[Robert Kaiser]

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 10

[Robert Kaiser]

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 11

[Robert Kaiser]

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 12

[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