We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜索 | 用户支持

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

详细了解

59.0 Rendering Issues

  • 3 个回答
  • 21 人有此问题
  • 1 次查看
  • 最后回复者为 epancini

more options

Since 59.0 there are rendering issues which makes the product unusable Generally, pages opens fine. Randomly, after a while, going back to an already open tab, the page will be almost blank. Moving the mouse will 'repaint' the disappeared images/text, by hovering over it

Windows7, AMD Radeon HD 5670 latest drivers tried both with and without hw acceleration in firefox performance options, doesnt fix. Previous quantum version was fine

Since 59.0 there are rendering issues which makes the product unusable Generally, pages opens fine. Randomly, after a while, going back to an already open tab, the page will be almost blank. Moving the mouse will 'repaint' the disappeared images/text, by hovering over it Windows7, AMD Radeon HD 5670 latest drivers tried both with and without hw acceleration in firefox performance options, doesnt fix. Previous quantum version was fine

被采纳的解决方案

so far it appears to be an issue that only affects users who have turned off cleartype font rendering within their windows settings. so a workaround for the moment would either be to turn cleartype back on or disabling hardware acceleration in firefox: Firefox's performance settings

定位到答案原位置 👍 1

所有回复 (3)

more options

Currently known issue:https://bugzilla.mozilla.org/show_bug.cgi?id=1435472 - a fix is being worked on!

more options

选择的解决方案

so far it appears to be an issue that only affects users who have turned off cleartype font rendering within their windows settings. so a workaround for the moment would either be to turn cleartype back on or disabling hardware acceleration in firefox: Firefox's performance settings

more options

Thanks for feedback Turning on cleartype is not an option for me. Is off for a reason. Contrary to what I initially said, disabling hardware acceleration in firefox actually FIXES the problem.

No need to say I'd like to use ha, as I assume makes rendering faster, but for the time being the product is at least back to usable