Comment 5 for bug 894133

Confirmed on an Android device in the office:


The result of that file depends on the Browser User-Agent, so we need to see a copy from the Android device itself to see what subset/transformed .ttfs are actually being sent from the Google Web Fonts.

Then we need to get those custom .ttfs and investigate whether the issue is just in those on Android, or occurs on raw versions used as a webfont on Android.