On Sat, 30 Mar 2013 at 20:21:27 -0500, joshua stein wrote: > I installed firefox36 and couldn't reproduce the problem on Freetype > 2.4.8 or our current 2.4.11, so I just compiled Firefox 12.0 > (-D2012-06-01) and it also looks fine. I'm compiling Firefox 17.0 > now (-D2012-12-01) and will see how it looks.
Ok, so this seems to be a Mozilla-only bug. I can reproduce the issue in Firefox 18.0.1, so apparently the problem started between the last 17 release and 18.0 and still exists in the current 19.0.2. I've filed a Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=856419
