Web font @ font-face rendering / anti-aliasing in Chrome and Firefox

I am familiar with the differences in rendering web fonts in different browsers and / or OS. A few questions:

I use a web font (woff) that looks like crap in Chrome but in FF (on Windows 7). The other day, I used my office computer from home through a remote desktop. I noticed that the font now looks like crap in FF. It looked the same as in Chrome in the office. (I have not tested Chrome at home). I know that remote desktop somehow reduces the "graphics", but not quite so, and I don’t know how this could affect the rendering of fonts. When I arrived at the office the next day, the rendering in FF was still messed up. I think the changes in the remote desktop session to the "graphics" were still in effect. I checked with Chrome, and now the rendering in this browser looks great, like in FF before !!? Therefore, I restarted the computer in order to return my usual “graphic settings”, but that did not help.Then I cleared the font cache and restarted again. Now I will go back to the crappy Chrome rendering and OK FF rendering.

My questions:

  • What happens to the “graphics” in general and the font display, in particular, when I connect to the remote desktop (setting = 32-bit color depth)? My guess is that no matter what has changed, it gets both FF and Chrome to use a different rendering method than before.

  • How can there be an effect after restarting the computer. Is the "rendering result" somehow stored in the font cache, as it seems? Seems strange.

Thanks for any advice.

+3
source share
2 answers

Chrome TrueType . WOFF OpenType TrueType, , , TrueType, . SVG Chrome ( ), WOFF OpenType.

, , , ClearType ( ).

. .

+7

, .

, 2012 (Roboto ).

, firefox, , ..

"desktop experience" 2012 .

2012:

"", "", " ". "", " " " " " ". "" " " "".

/, , - .

0

All Articles