56310 - Collapsing server causes all tree rows to disappear

Status: RESOLVED FIXED

(Core :: XUL, defect, P3)

Description

[Brian Ryner (not reading)]

On this morning's branch build (commercial):

1) Open mail, make sure you have the sidebar turned on.
2) Expand some server OTHER than your first one.
3) Scroll so that the tree row with the account name for this server (i.e.
[e-mail]) is at the very top of the folder list area.  Note that it
MAY be a prerequisite that the folders under this server take up the entire
display area at this point.
4) Collapse this server.

Result: The entire contents of the folder list area disappear!  This does not
seem to be a painting problem, rather, it actually looks like there are no
frames present.

I'm able to get the contents to reappear by doing a single line scroll (doing a
mousewheel scroll does NOT cause anything to reappear).  But, when the contents
reappear, there are often severe problems such as rows painting on top of each
other or the scrollbar thinking the tree is twice as high as it actually is.

Setting as severity Major, please raise to Critical if you think this
constitutes data loss.

Comment 1

[Brian Ryner (not reading)]

nominating rtm.  this can be pretty bad.

Comment 2

[Eric Vaughan]

There is no data lost. Scrolling to the top fixes everything. This only happens
if the folder is a the bottom of the display area.

Comment 3

[Brian Ryner (not reading)]

Well, it can present the appearance of data loss.  I can scroll up and down with
the mousewheel after this happens and nothing ever reappears until I do a
single-line scroll.  Also, the problem seems to be much worse when the collapsed
folder is at the top rather than at the bottom.

Comment 4

[Peter Trudelle]

rtm-, due to obscurity and easy workaround that should be obvious to anyone with
multiple servers who is collapsing one.

Comment 5

[Brian Ryner (not reading)]

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

Comment 6

[djk]

Is this a dup of bug 57139? (nevermind the higher number on that bug; it has 
patches attached.)

Comment 7

[Brian Ryner (not reading)]

No longer happens in current builds