3 ms·
Yet another case of chrome's bad rendering. The font used: http://www.google.com/webfonts/specimen/IM+Fell+English http://www.google.com/webfonts/specimen/IM+F
by xentronium 14y ago
Yet another case of chrome's bad rendering.
The font used: http://www.google.com/webfonts/specimen/IM+Fell+English http://www.google.com/webfonts/specimen/IM+Fell+English
Why would anyone try and use bad typewriter font imitation on a website is beyond me.
- ojiikun 14y agoIt's not just Chrome. I get just as awful a rendering on Firefox ESR 10.0.5 on Win7-64.
- jamesaguilar 14y agoErm. It seems like the problem is not with Chrome's rendering but with the site owner's font selection.
- petercooper 14y agoMore like Windows' bad rendering. It looks fine in my Chrome on OS X. A bit of a lame font but readable and not all flaky like the Windows screenshot linked by the original commenter.
- vacri 14y agoLooks fine in my win7/FF16 arrangement
- deleted 14y ago[deleted]
- joshuacc 14y agoChrome renders fonts differently than other browsers in Windows 7. Possibly for speed reasons? Both the latest FF and IE9 look decent.
- pcwalton 14y agoIt's more historical at this point. Chrome doesn't use DirectWrite because it uses Skia on Windows. At the time, the choice was between GDI+ and Skia, and Skia was much faster. But DirectWrite on Vista and 7 is extremely fast (it's GPU-accelerated, unlike the Skia backend Chrome uses).