256473 - a long list of options in 'select' gets truncated

Status: RESOLVED DUPLICATE of bug 256465

(Toolkit :: Form Manager, defect)

Description

[Jungshik Shin]

In the latest nightly and my own trunk build, a long list of 'select' in form is
truncated. 
A good example is bugzilla's 'target milestone' option. Go to any bug and move
up and down with the scroll bar. When you open it for the first time, the latest
milestone you can choose is '1.8alpha2' (although it has a few more options
including 1.8alpha3 and 1.9xxxx). After you move up with the scroll bar, the
latest you can choose is 1.0 (or something like that). 

This happened between 2004-08-20-05 and 2004-08-21-06

Comment 1

[Jungshik Shin]

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=MozillaTinderboxAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2004-08-20+10%3A00&maxdate=2004-08-21+18%3A00%3A00&cvsroot=%2Fcvsroot

There are a couple of suspicious check-ins..

Comment 2

[[e-mail]]

I don't see this in my linux gtk1 build.

Comment 3

[Jungshik Shin]

Hmm. it's odd. Can it depend on font (size, family, etc)/lang etc? 

I'm running 2004-08-21-06 (gtk1) on Linux and it has the problem. It also
happend with my trunk gtk2+xft build (updated just before I field this bug). I
tried with varga's check-in removed and it didn't help so that apparently, it's
not his.  

Somehow, it doesn't happen to 'Component' field of bugzilla although it has a
longer list of options than 'Target milestone'. There might be a magic number
that trigger this bug. 

Comment 4

[Jungshik Shin]

Another (possibly related to this) phenomenon I observed is that bugzilla page
sometimes gets truncated after I tried to submit my comment by pressing
'comment' button. Instead of submitting it, mozilla moves the cursor/focus up,
after which I cannot see anything below the first couple of lines of comment #0. 

Comment 5

[Jungshik Shin]

It's a dupe of bug 256465 (and what I described in comment #4 was filed as bug
256436). It seems like the fix for bug 255584 is to blame. 

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