Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 3 respostas
  • 0 tem este problema
  • 10 visualizações
  • Última resposta de 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?

Todas as respostas (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?