Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Rendering Bug on Adreno 308 GPUs from Version <=115 reappeared in 121

  • 3 biyano
  • 0 eza na bankokoso oyo
  • 10 views
  • Eyano yasuka ya Garrett24

more options

About half a year ago, there was a problem with parts of webpages being blocked out by rectangles in background colour on some Android devices. As I understand it, that was a problem with hardware optimization on Adreno 308 GPUs, as my phone has. The problem was fixed in 116.

Now, in 121 (and possibly earlier), the problem is back on my phone with this GPU.

E. g. on https://tvtropes.org/pmwiki/pmwiki.php/Main/ForgottenTrope, there is a white block in the second paragraph, hiding a part starting with the second half of the second line and two lines more. The text becomes visible line by line when I zoom in.

I found an entry in bugzilla, https://bugzilla.mozilla.org/show_bug.cgi?id=1843749, which seems to pertain to the problem. It was closed with the fix in 116. I guess it needs to be reopened, or a new one referencing this one?

What can I do to set the wheels in motion so the problem will be solved once again?

About half a year ago, there was a problem with parts of webpages being blocked out by rectangles in background colour on some Android devices. As I understand it, that was a problem with hardware optimization on Adreno 308 GPUs, as my phone has. The problem was fixed in 116. Now, in 121 (and possibly earlier), the problem is back on my phone with this GPU. E. g. on https://tvtropes.org/pmwiki/pmwiki.php/Main/ForgottenTrope, there is a white block in the second paragraph, hiding a part starting with the second half of the second line and two lines more. The text becomes visible line by line when I zoom in. I found an entry in bugzilla, https://bugzilla.mozilla.org/show_bug.cgi?id=1843749, which seems to pertain to the problem. It was closed with the fix in 116. I guess it needs to be reopened, or a new one referencing this one? What can I do to set the wheels in motion so the problem will be solved once again?

All Replies (3)

more options

Please create a new bug, you can mention 1843749 there.

more options

TyDraniu said

Please create a new bug, you can mention 1843749 there.

Me creating a bug on Bugzilla? 😮 Well, I can try...

more options

Garrett24 schrieb

TyDraniu said

Please create a new bug, you can mention 1843749 there.

Me creating a bug on Bugzilla? 😮 Well, I can try...

I did it, I created bug Bug 1874848. Don't know whether I did it right. Now I need to wait for someone to confirm it, I guess?