Fonts loaded in wrong order causes antialiasing problems

[GoogleCodeExporter]

What steps will reproduce the problem?

Problem title: How to make Chrome look like a bad font renderer
1. Windows 7, Firefox(latest), Chrome(latest)
2. Create a site with Droid Sans loaded from Google webfonts.
3. Check it out on both browsers. Chrome makes you puke.

What is the expected output? What do you see instead?

In Chrome you will see that there are raffled fonts. Cuts and scratches. 
No antialiasing! This happens with all fonts.

Please provide any additional information below.

If you would download the Droid Sans from fontsquirrel.com, then
you will have the power to open up the CSS, then change the load order of the 
fonts. 
SVG first!! 

This will make Chrome the absolute winner, when it comes to loading special 
webfonts.  Try it to experience it. 

I have made a pastie to give power to my words.  pastie.org/8095683

I have been posting this on several sites and have been an evangelist 
about this pastie for months now. I just realised that I can create an issue 
here :P  pretty shitty. 

Hopefully you people can fix this, because I love Chrome webfonts.. but all the 
fonts look shit on Chrome, so I need to find alternatives everyttime and create 
my own webfonts with a webfont-kit generator.

Yeah im so happy that I found this issue box. ! Love Xander

Original issue reported on code.google.com by xandersmalbil on 22 Jul 2013 at 6:55

[GoogleCodeExporter]

Any news yet?

Original comment by xandersmalbil on 23 Jul 2013 at 9:58

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

any news?

Original comment by xandersmalbil on 24 Aug 2013 at 9:48

• Added labels: ****
• Removed labels: ****