搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

Black boxes appearing throughout tabs after updating to version 87.0

  • 4 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 finlandsberet

more options

The other day, my browser updated to version 87.0, and ever since, I've been noticing black boxes appearing on various tabs. They go away if I scroll up or down the page they're on, or if I click on to another tab then back to the one I want. These boxes also appear over the tabs themselves at the top of the browser page.

Has anyone else noticed these? Will there be a fix for them in the near future - sooner rather than later?

Any help would be appreciated.

The other day, my browser updated to version 87.0, and ever since, I've been noticing black boxes appearing on various tabs. They go away if I scroll up or down the page they're on, or if I click on to another tab then back to the one I want. These boxes also appear over the tabs themselves at the top of the browser page. Has anyone else noticed these? Will there be a fix for them in the near future - sooner rather than later? Any help would be appreciated.

所有回复 (4)

more options

You can try to disable hardware acceleration in Firefox.

Close and restart Firefox after modifying the setting for changes to take effect.

You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.

more options

Thank you for such a quick reply! I did as you suggested, but it doesn't seem to have made any change. I can only assume that these black boxes appearing are a browser-related issue and not something else, like a security issue?

Would there be a fix from Mozilla's end sooner rather than later, do you think?

Thank you once again for your help.

由finlandsberet于修改

more options

Can you attach a screenshot?

more options

Unfortunately, I can't; it happens at random, and by the time I notice, the boxes/black spaces often vanish before I could react. This only started after my browser updated, as I mentioned in my original post. Assuming it's because of that, would it get fixed in the next update, do you think?