News for hackers. Stuff that matters.
Re:Why fonts look awful in Chrome, and how to fix it by paulirish on Friday December 21, 2012 @03:56PM (#4954482)
This is bad advice and against the recommendation of Chrome engineers amongst others.

The short version: http://lists.w3.org/Archives/Public/www-style/2012Oct/0014.h... The long version: https://code.google.com/p/chromium/issues/detail?id=152304

In addition: text rendering is very specific to the combination of browser & rendering layer. Targeting Mac Chrome with a webkit-wide property is a good way to get inconsistent results across your various desktop webkits and mobile webkits.

Re:Why fonts look awful in Chrome, and how to fix it by bicknergseng on Friday December 21, 2012 @06:08PM (#4955005)
Hey Paul... whenever certain CSS3 transition/animations run, custom fonts (typekit or google fonts... maybe others) will switch from the default subpixel aa to -webkit-font-smoothing: antialiased style aa for the duration, then switch back. From that second link, it's probably an OS X specific bug.