[Webkit-unassigned] [Bug 25581] New: maxCharWidth computation in SimpleFontDataMac.mm is smaller than Windows results
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue May 5 18:09:59 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=25581
Summary: maxCharWidth computation in SimpleFontDataMac.mm is
smaller than Windows results
Product: WebKit
Version: 528+ (Nightly build)
Platform: Macintosh
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: P2
Component: Layout and Rendering
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: ojan at chromium.org
CC: adele at apple.com, mitz at webkit.org, amanda at chromium.org,
agl at chromium.org
The numbers we get on the mac are often 10-20px smaller than the numbers we get
on Windows. This matters because it is one of the factors that makes our text
inputs smaller than IE on Mac WebKit.
Currently we grab the maximumAdvancement off the NSFont. On Chromium Linux
(which gets the same values as Windows for Windows fonts), we compute the
maxCharWidth as the xMax-xMin of the font by looking at the hmtx font table. Or
something like that. :) Amanda is working on a patch that tries to do the same
on the Mac.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list