29037 - Thread pane resizes after message is selected

Status: VERIFIED FIXED

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

Description

[Richard Zach]

The thread pane is larger on startup than after you select a message.

To reproduce:
1. Open Mailnews
2. Open folder
3. Select message

Actual result: the thread pane loses about three lines, now taken up by the
header area of the message pane.
Expected result: the height of the thread and message pane should stay the same.

Some may regard this as a feature: as long as the message pane is empty, you get
to see more message headers.  It can be quite annoying sometimes, though, e.g.,
when you select the wrong message.  If you click on a message but wanted to
click on the message below, you have to first scroll down, then click, to get
the right message.

Linux build 2000.02.23.08

Comment 1

[Richard Zach]

Attachment: Screen shot: before

Comment 2

[Richard Zach]

Attachment: Screen shot: after

Comment 3

[lchiang]

Do you think this has to do w/the problem with splitter bar overlapping into the 
thread pane's last entry?

Comment 4

[Richard Zach]

Are you asking me?  Hm, maybe it does.  Maybe the thread pane doesn't know that
the message pane extends a few lines north after you display a message and is
still painting rows where the message pane is now.  If so, then the real issue
seems to be this bug, and not the issue that the thread pane is peeking through
between the splitter and the message headers.

Comment 5

[lchiang]

Yep, I'm asking you, Richard :-)
I just wanted to see what you thought since your screenshot does show the 
overlap problem and it's in the general area of this bug report.

Comment 6

[Phil Peterson]

I'm guessing this is a splitter issue. Reassign to evaughan.

Comment 7

[Eric Vaughan]

I believe this is your bug. You need to set the pref size in you xul like we 
talked about.

-E

Comment 8

[Scott MacGregor]

Yup I have a fix for this in my tree. Ready to go when the tree opens for M15.

Comment 9

[Scott MacGregor]

I checked in the fix for this the other day.

Comment 10

[Richard Zach]

Right on.  Verified on Linux build 2000.03.17.08