271417 - preview plane blank after returning from multiple selection

Status: VERIFIED FIXED

(Thunderbird :: Mail Window Front End, defect)

Description

[Roy Paterson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla Thunderbird version 0.9+ (20041122)

After selecting multiple messages, selecting one message does not refresh the
(blank) preview pane.

Reproducible: Always
Steps to Reproduce:
1.Select a message A
2.Hold down shift and select a message B - preview pane goes blank
3.Release shift and click on message A again - preview pane still blank

Actual Results:  
the preview pane was blank

Expected Results:  
message A should be displayed in the preview pane

Comment 1

[David :Bienvenu]

confirming - this only seems to happen if you click on the message that was
displayed - I bet I'm not clearing the loadedmsg key when the message pane gets
cleared, so we think we're already displaying that message

Comment 2

[Mike Cowperthwaite]

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

Comment 3

[Mike Cowperthwaite]

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

Comment 4

[Mike Cowperthwaite]

Updating platform per dupe.

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

updating severity to normal, since this is really annoying.

note that this is not limited to thunderbird... but I guess the code is shared
between mozilla and tb?

Comment 6

[[e-mail]]

Attachment: Proposed patch

This seems to do the trick. I'm not actually sure which variables we need to
clear so I thought I'd play safe and clear them all.

Comment 7

[[e-mail]]

Fix checked in.

Comment 8

[Mike Cowperthwaite]

Verified fixed with Moz 1.8b-0120 and TB1.0+0302.

Comment 9

[Mike Cowperthwaite]

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

Comment 10

[Davor Cubranic]

I still see this bug in TB 1.0.6 (20050716)

Comment 11

[Mike Cowperthwaite]

(In reply to comment #10)
> I still see this bug in TB 1.0.6 (20050716)

That's because the fix isn't part of the 1.0 branch, nor is it going to be.

Comment 12

[Davor Cubranic]

Sorry, I understood the comment "verified fixed in TB1.0+0302" to mean that maintenance releases of 1.0 will include the fix.