Closed Bug 934962 Opened 10 years ago Closed 3 years ago
Thai font doesn't display on Galaxy S4 on Android 4
(Firefox for Android Graveyard :: General, defect)
(Reporter: eviljeff, Unassigned)
possibly a dupe to bug 896809 but was advised to log again. on a Galaxy S4 Firefox does not correctly display Thai font characters, but instead shows squares. This is reproducible on (at least) Firefox 26 and 27. Test case: http://www.thai2english.com/dictionary/hello.html Model GT-I9500; Android 4.2.2 (the stock version); Baseband I9500DXUBMF8 The problem appears limited to Firefox - the same website renders correctly in the preloaded 'Internet' app, and other apps (e.g. Facebook) also correctly render the font. If the Thai onscreen keyboard is enabled you can type in Thai in Firefox, but the characters turn to squares when rendered on screen.
10 years ago
Okay, just updated to 4.3 and Firefox works now. I'll leave it to someone else to decide if its worth trying to support 4.2.2 or if it should be wontfix'd.
Summary: Thai font doesn't display on Galaxy S4 → Thai font doesn't display on Galaxy S4 on Android 4.2.2
8 years ago
Mass change to move Firefox for Android::Readability bugs to block bug 1129033. Filter on readability-mass-move.
Component: Readability → General
3 years ago
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
3 years ago
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.