@Krish1980 While `font-smoothing` only works on Macs, `optimizeLegibility` has nothing to do with anti-aliasing. It enables OT features. I’m betting this has to do with a poor font choice for screen use.
how come some fonts may render and look smooth in Fireworks or Photoshop, but they turn jagged when implemented in the browser? I wonder if that is what Jarolin is referring too. I have wondered this for a while. If a software program can render them nicely, how come browsers can’t?
PS and Fireworks have four different settings that render type. Browsers don’t have this option. There are many causes for a font not to render well in the browser. This can be anything from the type designer choosing to auto–hint (manual hinting is a long and tedious process) which usually causes the font to look poor, more noticeably in small sizes (you see this a lot with GWF). Different font files can cause this as well (TrueType vs PostScript). Chrome also has a bug not rendering anti-aliasing correctly. So there’s not always one “thing” at fault.
i will go through my designs and see which ones did it.
the worst one i remember was “Comfortaa”: http://www.fontsquirrel.com/fonts/Comfortaa, but this was probably like 7 months ago, and I’m actually using it on a site now and it looks fine. But I know what I saw when I first used it, and it was ugly lol.