The mobile site and the mobile app don't use WebFonts. Many fonts don't support WebFonts anyway, but the mobile site should at least try to load them. Some phones are able to show WebFonts on the regular site.
Version: 1.0.0 (Android)
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T33805 Wikipedia Android App 1.1 tracking - current bugs | |||
| Resolved | None | T35802 Wikipedia Android app retains GPS access even when it doesn't need it | |||
| Resolved | • brion | T35208 Switch "near me" from Google Maps Android API to HTML-based OpenStreetMap backend | |||
| Invalid | None | T35855 Wikipedia Android App potential features (tracking) | |||
| Resolved | None | T35648 The mobile site and the mobile app don't use WebFonts |
IIRC the main limitation on Android is with complex script rendering; Android 4.0 at least is pretty capable, but on 2.3 the indic fonts for instance render incorrectly.
Possibly still better than boxes or blank pages though. :)
philinje wrote:
Let's add this as a JavaScript tiering function, meaning we can turn it on for some devices. Assigning to Patrick to think about.