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

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

  • 2 replies
  • 3 have this problem
  • 7 views
  • Last reply by 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?

All Replies (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.