Open
Bug 49166
Opened 24 years ago
Updated 7 months ago
Make sidebar default open/closed state for new window configurable
Categories
(SeaMonkey :: Sidebar, enhancement)
SeaMonkey
Sidebar
Tracking
(Not tracked)
NEW
People
(Reporter: uamjet602, Unassigned)
References
Details
Attachments
(1 obsolete file)
It would be nice if the opened/closed state of the sidebar for new windows would be configurable so I could open the sidebar in one window, and wouldn't have to close it in new windows as I don't want it open there. Something like: In new windows, the sidebar should be: ( ) Opened ( ) Closed ( ) The same as in the original window
Comment 3•24 years ago
|
||
Nominating for mozilla1.0. Reason: Some poeple have dozens of browser windows open, however, one sidebar is completely enough. I would like to open the sidebar for certain tasks, like searching and cheching news. Having the sidebar also open in the new windows I open (e.g. to follow links) while performing this task makes no sense.
Keywords: mozilla1.0
I have seen several complaints about the sidebar. This bug is a worthwhile request to improve its usefulness. The current behavior of the sidebar is more annoying than useful. With 'Closed' as the default, I think people will find the sidebar more enjoyable and will not wish to get rid of it, and to forget about it altogether: In new windows, the sidebar should be: ( ) Opened (X) Closed /* default */ ( ) The same as in the original window
OS: Linux → All
Hardware: PC → All
Comment 9•23 years ago
|
||
We should take this into consideration when redesigning sidebar. However, for default, we should continue to obey the most recent state of sidebar (open or closed). At this point I see no harm in offering a pref once we have a My Sidebar pref panel in place.
Comment 10•23 years ago
|
||
Just thought that another possible option could be "collapsed" (so that the presence of the slider can remind the user that the sidebar is waiting to be used...) In new windows, the sidebar should be: ( ) Opened ( ) Closed ( ) Collapsed ( ) The same as in the original window
Comment 11•23 years ago
|
||
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
Summary: [RFE] Make sidebar default open/closed state for new window configurable → Make sidebar default open/closed state for new window configurable
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: marlon.bishop → nobody
Priority: P3 → --
QA Contact: sujay → sidebar
![]() |
||
Comment 13•15 years ago
|
||
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
Status: NEW → UNCONFIRMED
![]() |
||
Comment 14•15 years ago
|
||
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•15 years ago
|
||
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•15 years ago
|
||
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 17•15 years ago
|
||
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 18•15 years ago
|
||
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 19•15 years ago
|
||
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 20•15 years ago
|
||
I think this bug is one prime reason why hardly any people use the sidebar.
Status: UNCONFIRMED → NEW
![]() |
||
Comment 21•15 years ago
|
||
It remembers the last state it was in right now, I don't think adding pref clutter is of any more use than what we're doing right now.
Comment 22•15 years ago
|
||
> It remembers the last state it was in right now
That's precisely why I fear opening the bookmarks or other sidebar panel: I open new windows routinely, and then I have to close the sidebar in several windows. I never want new windows to have the sidebar. With the current behavior, that means I don't use the sidebar at all. I think that applies to more people than me. Thus my last comment.
Attachment #9381448 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•