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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Why is Firefox 17.0 now using SmearType, and how do I turn it off?

  • 5 antwoorde
  • 21 hierdie probleem
  • 40 views
  • Laaste antwoord deur cor-el

more options

I updated to 17.0 today, and suddenly ClearType (what a joke!) is forced on, and I see no way to get rid of it. Seriously, ClearType is ugly and it makes it much harder to read webpages. This is the entire reason I refuse to install IE 9.0. Help?

OS: Windows 7 Pro 64-bit Browser: Firefox 17.0 32-bit Auto-updated 11/21/2012

ClearType was off in 16.0 and earlier. If it can't be turned I will have to revert.

I updated to 17.0 today, and suddenly ClearType (what a joke!) is forced on, and I see no way to get rid of it. Seriously, ClearType is ugly and it makes it much harder to read webpages. This is the entire reason I refuse to install IE 9.0. Help? OS: Windows 7 Pro 64-bit Browser: Firefox 17.0 32-bit Auto-updated 11/21/2012 ClearType was off in 16.0 and earlier. If it can't be turned I will have to revert.

Gekose oplossing

Temporary solution is disabling hardware acceleration in FF options. See this thread: https://support.mozilla.org/pl/questions/942265

Lees dié antwoord in konteks 👍 2

All Replies (5)

more options

Gekose oplossing

Temporary solution is disabling hardware acceleration in FF options. See this thread: https://support.mozilla.org/pl/questions/942265

more options

Thank you. Firefox is readable again.

more options

Try can also try to set the gfx.direct2d.disabled pref to true on the about:config page and leave hardware acceleration enabled.

more options

We have a patch in the works. It seems to be an azure issue. setting gfx.content.azure.enabled = False seems to work in the meantime. We aren't sure if the patch will be part of a chemspill or wait until 18. Thanks for being patient!

more options

(see: Bug 814101 - Font Issue in FF 17 -- please do not comment in bug reports)