Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox 59 is incorrectly rendering some of the sites (Doom9's Forum)

  • 2 回覆
  • 3 有這個問題
  • 7 次檢視
  • 最近回覆由 BugMaster

more options

After updating to Firefox 59 from Firefox 58.0.2 I have problem with page rendering at Doom9's Forum: http://forum.doom9.org/ The only option/workaround I have found to fix it is to disable (set to false) "browser.tabs.remote.autostart" which disables multiprocessor support (i.e. make it slower). I have even made video to show process to reproduce this bug with new clean Firefox profile and that "browser.tabs.remote.autostart" fix it: https://youtu.be/UXiZZyX0JAc Is there any other way to fix it without fully disabling multiprocessor support or rollback to Firefox 58.0.2?

After updating to Firefox 59 from Firefox 58.0.2 I have problem with page rendering at Doom9's Forum: http://forum.doom9.org/ The only option/workaround I have found to fix it is to disable (set to false) "browser.tabs.remote.autostart" which disables multiprocessor support (i.e. make it slower). I have even made video to show process to reproduce this bug with new clean Firefox profile and that "browser.tabs.remote.autostart" fix it: https://youtu.be/UXiZZyX0JAc Is there any other way to fix it without fully disabling multiprocessor support or rollback to Firefox 58.0.2?

所有回覆 (2)

more options

hi, thanks for reporting this. we are currently looking into this issue in https://bugzilla.mozilla.org/show_bug.cgi?id=1435472

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. Yes, looks like it the same problem and disabling hardware acceleration (gfx.direct2d.disabled = true) or enabling ClearType fix it. I probably will disable hardware acceleration (because ClearType was disabled for the reason at this PC) for the time before you will fix this bug.