Bug 94958
| Summary: | -webkit-font-smoothing: antialiased should use CG font rendering code path, not GDI | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Roger Fong <roger_fong> |
| Component: | CSS | Assignee: | Roger Fong <roger_fong> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | mitz, thorton, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
Roger Fong
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/12170072>
Roger Fong
*** This bug has been marked as a duplicate of bug 54004 ***