Closed Bug 53672 Opened 24 years ago Closed 24 years ago

Font size in some form widgets is too big

Categories

(Core :: Layout, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: pierre)

Details

(Keywords: regression)

Build ID: just pulled Form buttons, dropdowns and listboxes (<SELECT>'s) aren't properly adhering to the user's font choice. I currently have my Variable-width font size set to 16, and while the text of webpages is perfectly sized, the text in the aforementioned widgets is way too big. Ian says this is a very recent regression, and we're speculating that this may be a consequence of one of your recent checkins, Erik. Since this *highly* desirable to have for PR3 (form widgets will otherwise be unwieldly and unusable), could you please look into this ASAP (and maybe even back out any changes of yours that could have caused this?) Thanks.
Nominating for beta3 on the basis that these three important form widgets will be very hard to use (due to their very large font size) in PR3 if this isn't fixed, aside from the fact that they're excruciatingly ugly.
Hi Pierre, I guess you decided to check in Ian's *.css files even though I mentioned that the HTML form widget fonts were too big on Unix. I'm Cc'ing Waqar too, in case he has some ideas about how to resolve this. Perhaps we need to fix the system fonts on Unix so that they aren't so large in the HTML form widget context. If this bug shouldn't be assigned to you, please talk to Waqar since he knows that code.
Assignee: erik → pierre
note that I'm on windows, not *nix...
This is probably something to do with the code-level changes associated with my ua.css changes. I did _not_ see this on Windows with just my CSS files, but I _am_ seeing it now with my changed files plus the code level changes. I thought we had left the Win32 code alone?
rod's checkin fixed this
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
vrfy fixed in new win98 build
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.