70795 - Bookmarks window remembering its open/closed state between launches [suggestion]

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, enhancement)

Description

[Mike Stockman]

Basically, if I leave the Bookmarks window open when I quit Mozilla, I'd like it
to be open, and in the same location, when I launch Mozilla. Not too
complicated, at least from the user's standpoint... ;-)

Internet Explorer for Mac and iCab both do this, although iCab provides a
preference for having it open or closed at startup, and it's very convenient if
you use a non-docked Bookmarks window to navigate.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Setting status to new.  Over to XP apps: gui features.

This should probably be a preference if we do put it in...

Comment 2

[Claudius Gayle]

you could make this argument for every window no, where does it stop?

resetting component -->bookmarks

Comment 3

[Mike Stockman]

Well, since you ask, it doesn't need to stop at any of the "static" windows... if the user wants to keep bookmarks, history, Address Book, or any other windows with a fixed source of information (unlike, say, browser windows), why not let them?

Some browsers make it a preference (iCab for Mac OS), some just remember it (IE for Mac). I don't really mind either implementation, or think one is more/less usable.

Comment 4

[timeless]

Claudius: i agree w/ bz's move out of bookmarks.

however, to be fair i'm reassigning to UIDF instead.

opera allows people to opt to save or not. personally i think this is silly but 
i'm not the final arbiter.

Comment 5

[Claudius Gayle]

I don't think it's a bad idea... I don't care too strongly for it, but that's not solely my call.
My only concern was trying to limit prefs and if you started giving more windows this treatment
the pref would have to be all or none(cuz you couldn't have 1 per), then people would want more
windows w/ this behavior, yadda yadda yadda.
Anyway, isn't there some big huge honkin' RFE someone's working on in regards to mozilla
saving a whole lot of state across sessions, even after crashes and such? I wonder if that would
encompass this?
On a final, nit-picky note, as i re-read the component descriptions once again this could not have
been an XP Apps: _GUI_ bug. XP Apps, yes, bookmarks(a proper subset of xp apps) yes.
XP GUI, no. Doesn't matter now though as I think it has its correct home for now.

Comment 6

[Matthew T (active 1999-2002)]

The Right Way to fix this problem, I think, is to retire the 1980s-era ideas of 
`launch Mozilla' and `quit Mozilla' (as Internet Explorer for Windows has 
already done, to some extent). If you want a browser window, double-click the 
Navigator icon. If you want the Bookmarks window, double-click the Bookmarks 
icon. It makes as much sense to have the opening of those tied to each other, 
with or without a pref, as it does to have (for example) the opening of the My 
Computer folder on Windows tied to the opening of the My Documents folder. That 
is, no sense at all.

Comment 7

[Jonas Jørgensen]

.

Comment 8

[Andrei Boros]

One thing I might want to add is that Bookmarks window SHOULD CLOSE when closing
Mozilla (File->Exit or closing all other browser windows).

See behaviour of NS4.

Comment 9

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

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

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]

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 13

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

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

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

[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