Closed
Bug 291682
Opened 20 years ago
Closed 20 years ago
editable menulist font sizing and/or centering wrong on 120 lpi displays
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
RESOLVED
INVALID
People
(Reporter: johnrw, Assigned: jag+mozilla)
References
()
Details
Attachments
(1 file)
|
169.20 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 The googlebar uses an editable menulist for the search criteria control. We are getting numerous reports where font handling in higher resolution, which use the 120 lpi font set, are not displaying correctly in the widget. This is confirmed by me when using the standard theme. Reproducible: Always Steps to Reproduce: 1. Install Googlebar into a standard distribution browser. 2. Set display to 120 lpi fonts, and higher resolutions eg. 1920x1200 3. Type some search words into the Googlebar. Actual Results: text is incorrectly layed out. Expected Results: lay the text out better
| Reporter | ||
Comment 1•20 years ago
|
||
Updated•20 years ago
|
Summary: editable menulist font sizing and/or centering wrong on 120 lpi displays → editable menulist font sizing and/or centering wrong on 120 lpi displays
Comment 2•20 years ago
|
||
Dunno about you but the version of googlebar I fortunately happen to have downloaded earlier this month uses <hbox id="search-textbox" flex="1" persist="collapsed width" collapsed="false" maxheight="28" height="28"> Strangely enough maxheight="28" means what it says...
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 3•20 years ago
|
||
Thanks Neil. It had already been fixed in the last release, as we removed that section that specified a max height. Dunno where that came from, but maybe from the phoenix days... as I remember some problems with the widget that only occured on phoenix.
You need to log in
before you can comment on or make changes to this bug.
Description
•