1214461 - Severe font rendering issues on Medium.com

Status: RESOLVED DUPLICATE of bug 1144534

(Firefox for Android Graveyard :: Toolbar, defect)

Description

[Keunwoo Lee]

Attachment: tmp_13539-Screenshot_2015-10-13-20-37-14-915585918.png

User Agent: Mozilla/5.0 (Android 5.1; Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Build ID: 20150917151118

Steps to reproduce:

Visit the following URL:

https://medium.com/cuepoint/the-devaluation-of-music-it-s-worse-than-you-think-f4cf5f26a888


Actual results:

Font rendering is inexplicably blocky until you scroll down a lot. Font tendering also pops between crisp and blurry as you scroll up and down the page. See attached image. Reproduced through several reloads of the page. Didn't appear to be a timing issue--- I tried loading sans waiting quite a while.


Expected results:

Correct font rendering.

Comment 1

[Dirkjan Ochtman (:djc)]

I also saw this this morning, and I think I've seen it before. IIRC, it initially loads okay, becomes crappy on scrolling down, stayed crappy for a long while, then after scrolling quite far it returned back to normal.

Symptoms for me: pixelated font that is too bold. Somewhat harder to explain, some image rendering also seemed to be affected.

Comment 2

[u549602]

Samsung Galaxy S6 Edge (Android 5.1.1)
Samsung Galaxy Note 5 (Android 5.1.1)
Nightly 44.0a1

Following the reproduction steps stated in the bug description this issue could be encountered on latest Nightly (44.0a1 10-14-2015). 
Upon scrolling very fast on the given page, the blur can be noticed. 
If stopping the scroll action the blur is not present anymore, the page content is correctly displayed

Comment 3

[Brad Lassey [:blassey] (use needinfo?)]

Milan, looks like low res tiles, got an assignee?

Comment 4

[Milan Sreckovic [:milan] (needinfo for best results)]

To understand a bit better; the reporter sees this on 41 (release), and the situation is ok on nightly?  What's the device in the original report or comment 1?

Comment 5

[Keunwoo Lee]

The device in the original report is a 2014 Moto X running Android 5.1. I am running release, not nightly.

Comment 6

[Milan Sreckovic [:milan] (needinfo for best results)]

Would it be possible to run the nightly, so that we can narrow down if this problem is gone in that release and have a better chance of accelerating the fix through the Aurora and Beta?

Comment 7

[Keunwoo Lee]

Attachment: tmp_18325-Screenshot_2015-10-20-16-10-37-915585918.png

Seems fixed on nightly 44.0a1. Screenshot attached.