19605 - Resizing message/envelope pane causes thread pane scrollbar problems.

Status: VERIFIED DUPLICATE of bug 18193

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

Description

[laurel]

Using 1999-11-22-08m12 commercial builds on linux 6.0 and mac OS 8.5.1

Pardon if this is a duplicate, I didn't identify an existing bug to match this.

When you resize the message/envelope pane upward after having scrolled to the
bottom of a populated thread pane, the scrollbar functionality is messed up,
particularly the slider.

Steps to reproduce:
1.  Launch to messenger window. Leave the window and panes in default
proportions.
2.  Open an Inbox or other folder with lots of messages (my instances had 100 or
so). You want a folder with enough messages to list in the thread pane to have
to use the scrollbar/slider to get to the bottom of the list; enough messages in
the list to have to scroll 2 or three times the length of the visible thread
pane.
3.  Use the scrollbar's slider to get to the bottom of the thread pane list.
    The slider is at the bottom of the scrollbar, indicating you're at the
bottom of the list.
4.  Resize the message/envelope pane upward, drag the horizontal split bar up at
least several message lines.
5.  Select a message at the top of the thread pane.
    Notice the slider doesn't budge at all.
6.  Now try to scroll or use slider to get to the bottom of the thread pane.  It
is pretty hard to do.
    There are varied symptoms which appear:
         a.  Sometimes you can use the scrollbar's down arrow to scroll sloowly
downward, sometimes it doesn't respond at all. Sometimes it doesn't appear at
all.
         b.  Visually:  sometimes a great whitespace appears between the end of
the scrollbar slider and its own down arrow
         c.  Most often you cannot use the slider anymore to get down.

Usually you have to resize the thread pane back to initial size to get it back
functioning somewhat properly, or select another folder and return.

Actual result:  Impaired use of scrollbar/slider in the thread pane after
resizing the message/envelope pane.

Expected result:  Scrollbar should resize relative to the new thread pane size
and retain full functionality.

Comment 1

[laurel]

Looks like it may be something similar to bug #18420, but I don't know. I'll
assign to alecf and copy putterman and they can reassign if I messed up.

Comment 2

[Alec Flett]

no #18240 is about the thread view, not the message view. This seems to be
related to long subject lines.... adding rhp because this is really a mime
issue.
Rich, when the subject line gets too big in the header "toolbar", it causes this
whole window to be much wider. I think if we made the headers' "display" style
"inline" then the text would wrap and we wouldn't have that problem.

Investigating this now. If that doesn't solve the problem, I'll move this to M13

Comment 3

[Phil Peterson]

It sounds like laurel is talking about the scroll bar in the thred pane. If it
was really the message pane as alecf says, then this might be a dup of bug 18492.

Comment 4

[Alec Flett]

oops, phil is right. This might be a tree problem, I need to investigate more.

Comment 5

[Alec Flett]

actually, alot of tree, tree scrolling, and slider bugs have been fixed since
this was filed. Laurel, can you try playing around and see if any behaviors have
changed?

Comment 6

[laurel]

Using jan03 build on linux:
This seems to have gotten better in that using the slider or arrow works to get
to the bottom of the thread pane list even when the visible scrollbar/slider
proportion is screwed up.  However, the scrollbar/slider placement is incorrect
(doesn't readjust to new pane proportion) after moving the split bar upward.

So it's better but not fixed.

Comment 7

[laurel]

Windows seems better than linux, but does get into misrepresented slider
placement after a couple resizes. (I'm also noticing a real lag in pane resize
after a couple times on NT 4.0 and have gotten into some strange thread/msg pane
states as a result.)

Comment 8

[Alec Flett]

ok, the thumb sizing issue is actually in another bug. After talking with
Laurel, it seems that the rest of this bug is just a dupe of 18193.

Laurel says there are other crashes she's seen on Windows only, but behavior is
correct.

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

Comment 9

[laurel]

Marking verified as duplicate.