If you select Headers->All View then the buttons for "reply...", "forward...", "mark as junk" and the Trash icon are all too small until the more link is clicked on.

Not entirely sure why the "more" link is there as none of the email addresses appear to be cropped.

confirmed on linux.

A regression range (we surely didn't do that when I was doing the scrollbar for headers - all) would be lovely, even though I have a strong suspicion it'll point squarely at that calendar bug I reviewed in too much of a hurry.

Isn't present in the nightly 2008-12-16-03-comm-central but is in 2008-12-17-03-comm-central

When I say present, I mean the overflow event is being triggered (or possible the underflow event not being triggered) in 2008-12-17-03-comm-central. Whether the issue with "more" causing button size problems was there before then, I'll have to see if I can check.

Strange issue, I don't really understand why my changes caused this. Even when hiding the buttons totally, the multi-email field displays the more button. Clicking the more button causes the singleline=true attribute to be removed from the headerValueBox which causes that box to not overflow and not have a fixed height, but I don't know why on earth that would affect the button box next to it.

Same happened to me on OS X while reading a post in md.planning from Matthew Zeier about the scheduled downtime.

Also, clicking on "more" it changes the spacing between the fields (between from and subject). I do not see the usefulness of the "more" button as it does not display anything else.

The Thunderbird drivers wish to release Thunderbird 3 as soon as possible. As a result, we feel that this bug shouldn't stand in the way of all the other good work getting into the hands of users sooner rather than later. Therefore we are retargeting it for 3.1. See http://ccgi.standard8.plus.com/blog/archives/242 for more details. The 3.1 release is expected to be a quick release soon after Thunderbird 3.

I'm not seeing this happen anymore with our current buttons. Are people still seeing this issue on nightly releases?

I'm not seeing this either; removing the blocking-3.1+ flag until we have some reason to believe this bug is still around and effects a lot of people. If that should happen; feel free to renominate. Otherwise, this is likely to be a WORKSFORME...

Yes, WORKSFORME now (even on a build a few months old 20090615)