307163 - When collapsing an account while not at topmost scroll position, scrollbar disappears and empty folders appear

Status: RESOLVED FIXED

(Thunderbird :: Mail Window Front End, defect)

Description

[Adam Guthrie]

In a profile with multiple accounts that allow you to scroll the account pane
when all the accounts are expanded, this is reproducible. (This was reproduced
in a clean profile.)

1. Expand all the accounts so you get a scrollbar.
2. Scroll to the bottom of the window (or anywhere that's not at the top). 
3. Click on a visible twisty of an account, or double click that account to
collapse it.

Three blank folders appear at the top of the account pane and the vertical
scrollbar disappears. The only way you can get the scrollbar to appear (and the
folders to go away) is to use the middle mouse button and scroll up. Up/down
arrow keys and Home/End have no effect. 

I really don't see this as a major issue, seeing as how most people don't use
that many account, and the fact that there's an easy work-around, but I'd like
to figure out why this is happening.

This didn't occur in 1.0.

Comment 1

[Adam Guthrie]

Attachment: what the account pane looks like after weird repaint

Comment 2

[Adam Guthrie]

Attachment: normal view of the account pane

Comment 3

[Scott MacGregor]

build ID :) branch or trunk?

Comment 4

[Adam Guthrie]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20050905 Firefox/1.6a1
Thunderbird: version 1.6a1 (20050906)

This seems to be an issue only on trunk builds (oddly enough). Couldn't
reproduce with version 1.4 (20050906). :)

Comment 5

[Scott MacGregor]

this looks an awful lot like the regression caused by Bug 304904 which was
backed out. See Bug 305900

Comment 6

[Adam Guthrie]

Sure does. I didn't verify it myself (by backing the patch out), but this
certainly looks the same as the other issue. I'll leave this open and resolve it
after I verify this is fixed after the new patch for bug 304904 lands.

Comment 7

[Tuukka Tolvanen (sp3000)]

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

Comment 8

[Adam Guthrie]

Just verified that this was fixed by the check-in for bug 304904.