Closed Bug 138319 Opened 24 years ago Closed 23 years ago

Incorrect vertical positioning for fonts with Freetype enabled

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: s.vassall, Assigned: bstell)

Details

Attachments

(2 files)

Build ID: 2002041711 (Mozilla RC1) Platforms: Linux Freeype build: 2.0.9 (Hinting complied it) Moz settings: Freetype enabled Autohinting off Unhinted off (i.e. Hinting on) When Freetype is enabled then Mozilla renders it UI with AA. However the font is incorrectly vertically positioned; moved up a few pixels. On occassions text can even be made to jump vertically in the URL bar. This is particularly apparent in the preferences dialog, but applies to the whole browser UI. Since TrueType AA is an eye-candy type of feature it is a shame if moz1.0 was to ship with this bug that destroys the eye-candy.
Note the positioning of text within the OK, Cancel, and Help buttons. The bug can also be seen in the category window, with each item slightly out of line with either the dotted line, or the twisty.
reporter (Stefan Vassall): can you reproduce this bug with a recent build of mozilla (for example, 1.1beta)? if so, please comment again with details. if not, please resolve this bug as WORKSFORME. thanks.
-> layout. this is not an uid issue.
Assignee: mpt → attinasi
Component: User Interface Design → Layout
QA Contact: zach → petersen
I can still reproduce this bug with Build ID: 2002080508.
Screenshot of the behaviour with the latest builds. Font is set to use Freetype support, i.e. in the Font prefence dialog Agfa-Monotype-times-new-roman-iso8859-1
Is this still a problem in current builds?
->Fonts & Text
Assignee: attinasi → font
Component: Layout → Layout: Fonts and Text
QA Contact: petersen → ian
->Gfx.
Assignee: font → bstell
Component: Layout: Fonts and Text → GFX: Gtk
is this the direct FreeType code or the Xft code? (eg: direct freetype => pref("font.FreeType2.enable", true);)
"Reporter: Can you reproduce this bug with a recent build of Mozilla (for example, 1.4 RC1)? If so, then please comment again with details. If not, then please resolve this bug as WORKSFORME. Thanks."
no word from reporter in nearly a year. marking WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: