RESOLVED INVALID 117214
[Win] Font rendering turns jaggy after hardware acceleration 
https://bugs.webkit.org/show_bug.cgi?id=117214
Summary [Win] Font rendering turns jaggy after hardware acceleration
Elaine F
Reported 2013-06-04 15:59:27 PDT
Created attachment 203733 [details] Simple bugfile - with CSS Filter (hardware accelerated) 1. Open font.html (attached). This file has a single web font with a CSS Filter attached, which forces hardware acceleration 2. Open font-nofilter.html (attached). This file is identical to the first one, which has the CSS Filter removed 3. Edit font.html to remove the CSS Filter and add another CSS reference that will force hardware acceleration, such as translateZ(0). The font is jaggy after the hardware acceleration is turned on. Not reproducible on Mac. Please see attached screen shots - one is a comparison to other major browsers (IE and Firefox) using the same file, and the other is hardware accelerated vs. non hardware accelerated.
Attachments
Simple bugfile - with CSS Filter (hardware accelerated) (524 bytes, text/html)
2013-06-04 15:59 PDT, Elaine F 		no flags
Details
Sample - no hardware acceleration (492 bytes, text/html)
2013-06-04 15:59 PDT, Elaine F 		no flags
Details
Comparison with other major browsers (90.93 KB, image/png)
2013-06-04 16:00 PDT, Elaine F 		no flags
Details
Comparison between hardware accelerated and non-hardware accelerated (5.54 KB, image/png)
2013-06-04 16:05 PDT, Elaine F 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Elaine F
Comment 1 2013-06-04 15:59:56 PDT
Created attachment 203734 [details] Sample - no hardware acceleration
Elaine F
Comment 2 2013-06-04 16:00:33 PDT
Created attachment 203736 [details] Comparison with other major browsers
Elaine F
Comment 3 2013-06-04 16:05:24 PDT
Created attachment 203737 [details] Comparison between hardware accelerated and non-hardware accelerated
Elaine F
Comment 4 2013-06-04 16:06:40 PDT
Tested both on Chrome canary (Version 29.0.1528.2 canary) and Chrome release (Version 27.0.1453.110 m)
Elaine F
Comment 5 2013-06-05 12:04:44 PDT
Moved to the Chromium issue tracker: http://code.google.com/p/chromium/issues/detail?id=247090
Note You need to log in before you can comment on or make changes to this bug.