Currently, in May 2013, even 11 months after the bug was reported, it's not solved. This is a big bug in Google Chrome and the Google Chrome Team does know about this, see the official bug report here.
Webkit font smoothing how to#
If you want to be updated on this issue, have a look on the according blog post: How to fix the ugly font rendering in Google Chrome. RGBa solution (found in Jasper Espejo's blog): text-shadow: 0 0 1px rgba(51,51,51,0.2) I made a blog post on this: There's also an outdated possibility: Give the text a simple (fake) shadow: text-shadow: #fff 0px 1px 1px Or the RGBa syntax (by nezroy, found in the comments! Thanks!) -webkit-text-stroke: 1px rgba(0,0,0,0.1) So, the way to fix those fonts is simply giving them -webkit-text-stroke: 0.Xpx Third row has: -webkit-text-stroke: 0.6px See how the example from the initial question look today, in Chrome 29: POSITIVE EXAMPLE:įixing the above screenshot with -webkit-text-stroke:įirst row is default, second has: -webkit-text-stroke: 0.3px
Webkit font smoothing free#
I've written a large blog post on that issue, feel free to have a look: How to fix the ugly font rendering in Google Chrome Reproduceable examples
As there have been several huge changes in the rendering engine there's obviously something in progress. There is also an (unproven) solution that recommends using only TTF/OTF fonts as they are now supported by nearly all browsers.ģ.) The Google Chrome developer team works on that issue. I would feel bad to simply copy his excellent answer, so please have a look there. However, there are some CSS tricks that will "smoothen" the rendered font a little bit, you'll find the workaround(s) deeper in this answer.Ģ.) There IS a real solution for this when self-hosting the fonts, first posted by Jaime Fernandez in another answer on this Stackoverflow page, which fixes this issue by loading web fonts in a special order. Surprisingly all other font file types render beautifully. woff files from Google's API which render horribly. The problem is that Chrome simply requests. See example comparison of current stable Chrome 35 and latest Chrome 37 (early development preview) here:ġ.) There is NO proper solution when loading fonts via 
Status of the issue, June 2014: Fixed with Chrome 37įinally, the Chrome team will release a fix for this issue with Chrome 37 which will be released to public in July 2014.
0 kommentar(er)
