top | item 3444301

(no title)

hm2k | 14 years ago

TIL Google Chrome doesn't support OpenType.

discuss

kooshball|14 years ago

I wonder if this explains the ugly non-aliased text I see so often with chrome.

masklinn|14 years ago

I'm pretty sure that's the renderer and has nothing to do with opentype support.

tadfisher|14 years ago

The render is OS-dependent. On which operating system do you experience this issue?

rorrr|14 years ago

Chrome does suck at rendering. Not just the fonts. I recently found a bug where Chrome constantly eats 12% of an 8-core CPU because of an animated GIF, some transparency and shadows. The latest IE and FF have no such problems.

I'm a Chrome user btw.

mrlase|14 years ago

Kind of disappointed, really. I wonder if the font rendering really is better in FF? I hardly open it anymore other than to browse sites that I feel to be shady (as I have FF much more hardened than Chrome).

bzbarsky|14 years ago

Well, Firefox enables "common" ligatures by default, unlike Chrome. so yes, font rendering does tend to be better in Firefox....

troymc|14 years ago

Similarly, it doesn't seem to work in Safari on my iMac, or in Safari on my iPad 2. (This isn't surprising given the names of the CSS selectors, i.e. -moz-stuff and -ms-stuff but never -webkit-stuff.)