Closed
Bug 104048
Opened 23 years ago
Closed 15 years ago
Go To Message Folder opens new three-pane view
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: blandoon, Unassigned)
References
Details
(Whiteboard: [need info])
Build ID: 2001101003 on win32
The Go To Message Folder button (see bug 56419) behaves strangely when used to
search newsgroup messages.
For example, if I have the three-pane thread view open to, say,
netscape.public.mozilla.general, and I Search Messages by subject, I eventually
get a Results window with a list of matching results. If I select one message
and click the Go To Message Folder button, it opens a brand new three-pane view,
which promptly refreshes the new message counts from the server, and does
nothing else. It also fails to display the message I had previously selected,
but I think this aspect is covered in bug 103780.
The expected behavior would be that the selected message appears highlighted in
the Thread pane of the existing window, if any, and is displayed in the Message
pane below (I apologize if I don't have the terminology exactly right). This was
the behavior in Communicator 4.x.
Reporter | ||
Comment 1•23 years ago
|
||
adding cc, per request in n.p.m.mailnews.
Just some background info: 4.x doesn't open a new window regardless of the
window settings pref; Go to Folder in 4.x goes to message in current mail
window.
Updated•23 years ago
|
Updated•23 years ago
|
Priority: -- → P3
*** Bug 119695 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
Comment 5•23 years ago
|
||
This is an annoyance for me too, but for mail. I want the 'Open Message Folder'
to use an existing window if there is one with that folder already open; as per
NS 4.X behaviour.
Max.
Comment 7•23 years ago
|
||
Shouldnt this bug have the 4xp keyword?
Comment 8•22 years ago
|
||
The spec (http://mozilla.org/mailnews/specs/search/) does not specify whether a
new window should appear or an existing window. I would expect it to adhere to
the Mail & News/Windows, preference setting:
"When opening messages, display them in:
- A new mesage window
- An existing message window"
Whiteboard: [need info]
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
Updated•17 years ago
|
Severity: normal → minor
QA Contact: laurel → search
Updated•16 years ago
|
Assignee: mail → nobody
Priority: P3 → --
QA Contact: search → message-display
![]() |
||
Comment 10•16 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 11•15 years ago
|
||
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
Comment 12•14 years ago
|
||
Ever confirmed: true
You need to log in
before you can comment on or make changes to this bug.
Description
•