241555 - Selecting multiple messages should empty message preview

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[Erik Arvidsson]

When selection multiple messages in the thread pane using the mouse, the message
pane is made empty. The same thing does not happen when using the keyboard to
select multiple messages.

Steps to reproduce:

1. Select a message
2. Hold down shift and press down or up arrow to select multiple messages
3. The first message is still shown in the message pane

Expected result:

The message pane should be empty if more than one message is selected no matter
what way the messages were selected.

This causes bug 233027 where multiple selected messages get read even though
they were never shown/downloaded/read.

Comment 1

[Lucas Panjer]

I would much prefer that both of these cases show the last selected message in
the multiple message selection. This is one of the few remaining daily-use
features I miss from OE. It is rather useful when you need to quickly scan a
bunch of messages with which you are likely to take the same action (ie.
delete). It lets you read each message and then select the action once.

Comment 2

[Mike Cowperthwaite]

*** Bug 257760 has been marked as a duplicate of this bug. ***

Comment 3

[Csaba Gabor]

Here is a more detailed, specific behaviour:
Select a message with the mouse from the message list (in the thread pane).  The
message isplays in the message pane.

Now, while holding the control key down, select another message.  The message
pane becomes blank (I agree with previous posters that it should not.  Either
show the original message or (preferable) show the most recent message added).

Now if the original message is made the only selection (by either clicking it,
or by clicking the second message with the control key pressed), the message
pane continues to stay blank.

(This is on Win XP Pro, SP2)
Csaba Gabor from Vienna

Comment 4

[Erik Arvidsson]

This one now works as supposed according to how the bug was originally reported.
Some of the commenters wanted alternative behavior but please reopen bug 257760
which was incorrectly marked as a duplicate of this one (different behavior wanted).

Comment 5

[Mike Cowperthwaite]

Reopened to fix resolution.  Erik Arvidsson, please do not use Fixed unless you 
can point to a specific patch that solved the problem.