Bug 94958 - -webkit-font-smoothing: antialiased should use CG font rendering code path, not GDI
Summary: -webkit-font-smoothing: antialiased should use CG font rendering code path, n...
Status: RESOLVED DUPLICATE of bug 54004
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Normal
Assignee: Roger Fong
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2012-08-24 11:05 PDT by Roger Fong
Modified: 2012-08-24 11:19 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Fong 2012-08-24 11:05:44 PDT 
When specifying -webkit-font-smoothing: antialised; the code path ends up using GDI to draw the text. 
Firstly, this causes a lot of transparency issues since GDI has no concept of an alpha channel.
Secondly, in the code path, GDI ends up drawing subpixel antialiased text, not aliased text anyways.

The CG code path also has the capability of drawing antialiased text. The reason that the GDI path was used in the first place is no longer a concern here so we can stop using the GDI code path.

I'll be getting rid of the GDI code path so that font rendering on windows only uses CG code path for font rendering, instead of sometimes using CG and sometimes using GDI.
Comment 1 Radar WebKit Bug Importer 2012-08-24 11:06:03 PDT 
<rdar://problem/12170072>
Comment 2 Roger Fong 2012-08-24 11:19:44 PDT 

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