Closed Bug 197137 Opened 18 years ago Closed 16 years ago

Replying to a threaded message sometimes replies to the wrong message in that thread

Categories

(MailNews Core :: Composition, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ngrover, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021203
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021203


If you have a collapsed thread and you double-click on the first message, that
message will be opened in a separate window. While that message view window is
open, if you expand the thread in the message list and then double-click on
another message in that thread, this message will replace the previous message
in the already open message view window. When you try to reply to this message,
the message compose window will be setup to reply to the message that was first
opened when the thread was still collapsed, not the message you're currently
viewing.

Reproducible: Always

Steps to Reproduce:
(1) Organize your messages in threaded mode.
(2) Start with the thread collapsed.
(3) Double-click on the first message to open it in a separate message view window
(4) While that message view window is open, expand the thread in the message
list, and double-click on another message in the thread - this message will
replace the previous message in the already open message view window.
(5) Use Reply (Ctrl-R) or Reply-All (Shift-Ctrl-R) to reply to the message, and
the compose window that opens will quote the message at the top of the thread
(the message that was first opened when the thread was still collapsed) *not*
the message you're currently viewing.
Actual Results:  
The compose window that opens will reply to the message at the top of the thread
(the message that was first opened when the thread was still collapsed) *not*
the message you're currently viewing.

Expected Results:  
The compose window that opens should reply to the message that you're currently
viewing.
If I expand the thread in the message list *before* opening any of the messages
for viewing, then the reply function will use the appropriate message (whichever
one I'm viewing at the time).

The trigger seems to be the expand/collapse state of the thread in the message
list *when the first message is opened for viewing*. If I start expanded, open a
message, then collapse the thread, the reply still works properly.
Blocks: 236849
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
No longer blocks: 236849
You need to log in before you can comment on or make changes to this bug.