Closed Bug 50748 Opened 25 years ago Closed 15 years ago

mail sidebar links open a NEW browser window EVERY time

Categories

(SeaMonkey :: Sidebar, defect, P3)

Product:
SeaMonkey
Component:
Sidebar
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
Future

People

(Reporter: cmaximus, Unassigned)

Details

***Overview Description: This bug is the offspring of bug 44797. In that bug, when a link form the mail sidebar was clicked, in the case when a browser window wasn't open, nothing happened. When a browser window was open, it was used to load the link. Now, a new browser window is opened every time, regardless. This is overkill and breaks the previous behavior(use the available window) ***Steps to Reproduce: 1) Open a browser window. 2) Open mail. 3) Click on a link from the mail sidebar. ***Actual Results: A new browser window is opened ***Expected Results: Only open a new window if there isn't one available, otherwise use the already opened one. ***Build Date & Platform Info: all platforms with the 2000082508 builds. ***Additional Information: This may be misassigned - i'm simply piggybacking off of bug 44797
I think this is an application policy issue,and doesn't really belong in a widget toolkit. However, after discussion with DanM, Claudius and SLamm, I'm futuring this. The current behavior is reasonable, sidebar links still open in current window when possible, and there is no loss of function or other severe consequence ->future.
Target Milestone: --- → Future
Reusing browser windows is evil, imo. (see bug 35578)
spam : changing qa to sujay (New Sidebar QA)
QA Contact: shrir → sujay
See also bug 27162, default link target [from sidebar] should be most recently used browser.
Also happens on Windows ME and is annoying as hell. IMNSHO should go back to old behaviour or be configurable. Normal usage would be: you have an open browser window, you open the bookmarks sidebar, (because you want to go to another site) and click, but now you end up with the original (blank) window, plus a new one with your selected site. Should be raised in priority as it will stop a lot of people using the sidebar. It's just plain rude to open multiple new windows.
Another point - it is inconsistent behaviour for the bookmarks in the sidebar to behave differently from the same bookmarks in the bookmark menu. It obviously would make no sense for a bookmark chosen from the menu window to open in a new (rather than the current) browser window, so why should it be different for the sidebar? This change in behaviour has really made the sidebar annoying instead of useful, and should be changed back asap.
John: I'm using 2001 120703 on Win98, and clicking a bookmark in the navigator sidebar doesn't open a new window. You might be using a build from right after bookmarks switched from tree to outliner. This bug is about using the mail sidebar, in which case reusing a window is the more "rude" behavior, because then the user has to hit the back button to make sure the window used didn't have unsaved information in it.
My apologies - I didn't read the "mail" part correctly. I am using build 2001120603. I will check the latest build as soon as it is available (20011207 appears to be corrupt on the FTP site) and log a new bug if the navigator sidebar still opens a new window.
Blocks: 125953
No longer blocks: 125953
Blocks: 125953
Is there any point in keeping this bug open? Sidebar in mailnews was permanently removed on Sept. 14th 2002.
Product: Browser → Seamonkey
Assignee: danm.moz → nobody
QA Contact: sujay → sidebar
No longer blocks: 125953
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
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
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
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
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
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
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
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
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
(In reply to R.K.Aa. from comment #9) > Is there any point in keeping this bug open? > Sidebar in mailnews was permanently removed on Sept. 14th 2002. Messenger sidebar might be coming back some time, but here is surely dead. "Fixed" by the messenger sidebar removal.
Resolution: EXPIRED → FIXED
You need to log in before you can comment on or make changes to this bug.