Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I notice that the text on some web pages look bad when viewed in Chrome (16.0.912.77 m) while OK with Firefox (10.0). FWIW, I'm using the Windows versions of those applications, with default settings.

As an (ironic) example, www.google.com/webfonts.

Does someone know why that is, and if something can be done about it?

Thank you.


Edit: Another example:

enter image description here


Edit: Here's how it looks in FireFox:

enter image description here

share|improve this question
1  
Screen shots might be a better way of illustrating the problem. –  ChrisF Feb 8 '12 at 22:39
    
Sorry about that. Done. –  OverTheRainbow Feb 8 '12 at 22:47
    
It only occurs on some web pages. XPSP3, running the latest Chrome browser. The same page looks slick on Firefox. –  OverTheRainbow Feb 9 '12 at 0:05
1  
I added a screenshot as viewed in Firefox. It's easier to read. How can I get Chrome to render pages the same way? –  OverTheRainbow Feb 9 '12 at 1:11
3  
Can you upload .PNG screenshots. The JPG compression is not helping. –  iglvzx Feb 9 '12 at 4:24

2 Answers 2

I was looking for a solution for exactly the same thing: to make chrome render better. It was horrendous compared to Firefox, IE, and safari in windows (software rendering mode in Safari renders like on a mac,but it's a bit slow).

The reason why Firefox and IE9 render well is because they use DirectWrite hardware acceleration to render the fonts.

It's been suggested to turn off the GPU acceleration in Chrome. But it doesn't work. I found a good enough solution, where the text will be rendered LEGIBLE (didn't say anything about being fully antialiased and beautiful):

REMOVE THE WOFF LINE AND SVG LINES!!!!

@font-face {
    font-family: 'SomeFont';
    src: url('../fonts/SomeFont.eot?#iefix') format('embedded-opentype'), 
         url('../fonts/SomeFont.ttf')  format('truetype');
    }

What I found was that Chrome can do TTF render better, but choose to look for WOFF files first. So you only need EOT and TTF files.

share|improve this answer

Chrome uses Windows for font rendering. It's far worse on the Windows 8 beta than anywhere else - enough that it almost seems to be a swipe at Google. Firefox uses its own font rendering method, which makes the browser heavier but avoids the problem.

If tuning your ClearType doesn't help, there's not much you can do.

Ironically, IE9+ has the best font rendering of any browser engine. In other words, even Microsoft refused to use their own crappy font engine when it comes to the www.

I'm not sure why Chrome hasn't put together a better solution yet.

share|improve this answer
    
Are you sure that's how Chrome works? It doesn't even obey DPI settings. –  Louis Jul 21 '12 at 1:20
4  
In other words, even Microsoft refused to use their own crappy font engine when it comes to the www IE9+ uses DirectWrite, which is Microsoft's own "font engine". –  ta.speot.is Sep 23 '12 at 2:42
    
Font quality is fine in Chrome on Mac, so it must be related to OS provided font rendering. –  Lea Hayes Oct 15 '12 at 15:37

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.