29673 - Click on header, message doesn't load after being in just thread pane mode

Status: VERIFIED DUPLICATE of bug 24468

(SeaMonkey :: MailNews: Message Display, defect, P3)

Description

[Akkana Peck]

As of yesterday's build, mail has been basically unusable for me because most
messages won'd load in the message pane.  I can read a few messages, then I
click on the next header in the thread pane, and nothing happens in the message
pane -- it goes on showing whatever message was there before.  If I click around
on other messages after that, most other messages also won't load, but a few will.

This is a regression -- mail was working fine last week.  I started seeing this
problem in Monday's build.

Comment 1

[lchiang]

bug 29650 is pretty much the same, I think.  You need to back out of rpott's 
change as per the other bug

Comment 2

[Akkana Peck]

Thanks, Lisa, sounds like the same bug.  I'm a'duping ...

*** This bug has been marked as a duplicate of 29650 ***

Comment 3

[lchiang]

Ok.  I'll mark verified as duplicate..  You can work around it if you backup of 
that change as per the other bug.

Comment 4

[Akkana Peck]

Reopening -- I'm still seeing this after getting Scott's changes, and he says
this is probably a different bug after all.

Here are the circumstances where I tend to see this:

I'm in a 3-pane view, near the end of my inbox with only 2-3 messages showing in
the thread view (because I've been deleting messages from the end of the folder).

I want to see more messages, so I click on the splitter to close the message
pane and see only the thread pane.  I still see only 2-3 messages, so I click on
the scrollbar trough a bunch of times to scroll up and see more messages.

Eventually I see a message I want to read, so I click on it (I'm still in
header-pane-only mode), then I click on the splitter.  The message pane opens
up, and I see the headers of the message, but no message body.

Now I'm in a mode where I can't load any message body -- clicking on the message
above or below the one I want loads the headers for that message, but not the body.

Comment 5

[Akkana Peck]

Reassign to Scott -- just talked about it by phone.

Comment 6

[leger]

Putting on PDT+ radar.

Comment 7

[Scott MacGregor]

Clarifying the subject. The problem only occurrs after you've collapsed the
message pand and then bring it back and try to display another message.

we aren't loading the message body.

Sounds like a problem in our JS where we aren't properly detecting that the
message pane is back when we uncollapse it.

Scott, can you take a look?

Comment 8

[scottputterman]

I'll look, but if were weren't detecting it, why would we load the headers?

Comment 9

[scottputterman]

try resizing it.  it makes it work for me.

Comment 10

[Scott MacGregor]

Oh wait...good point =). We must be loading the url for the message then. i
can't think of why mime would bail out when showing the body in this case
either. Adding rhp.

Comment 11

[Scott MacGregor]

The problems pretty easy to reproduce. You just need to collapse the message
pane, click on a few headers. Expand the message pane, click on another header
and notice that the body is never displayed only the headers in the message
pane. weird

Comment 12

[Scott MacGregor]

resizing makes it come back for me too.

I really don't think this is a PDT+ issue. Removing the label for re-evaluation.
It only happens when you collapse the message pane and bring it back.

Comment 13

[scottputterman]

I'm reassigning this to trudelle since I think this may be an xpfe bug.  The 
message pane isn't showing up until the window gets resized. I'm told that we 
never hide it, so in theory it should come back.

this also probably shouldn't be PDT+ since there is a workaround, though if 
someone had a fix it would be good to take.

Comment 14

[lchiang]

The remaining case akkana outlines is a duplicate of 
http://bugzilla.mozilla.org/show_bug.cgi?id=24468.

Comment 15

[lchiang]

I think we should then mark this bug dup again as originally marked and use the 
other bug to continue to track akkana's case.

Comment 16

[Scott MacGregor]

this is indeed a dup as lisa pointed out.


*** This bug has been marked as a duplicate of 24468 ***

Comment 17

[lchiang]

verified