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!

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

Problem with bold letters / solved on safe mode. not solved when I manually disable all extensions

  • 2 respostas
  • 3 have this problem
  • 13 views
  • Last reply by Lost10

more options

Example:

"Weird" bold letters: http://i56.tinypic.com/2it5th5.jpg

Normal bold letters: http://i55.tinypic.com/2num39u.jpg

How can I solve this?

Example: "Weird" bold letters: http://i56.tinypic.com/2it5th5.jpg Normal bold letters: http://i55.tinypic.com/2num39u.jpg How can I solve this?

Lost10 modificouno o

Chosen solution

In Firefox 4 and later Safe mode disables extensions and disables hardware acceleration.

  • Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"

If disabling hardware acceleration works then check if there is an update available for your graphics display driver.

If you have an ATI graphics display try to disable "Morphological Filtering" in the Catalyst display driver:

  • Catalyst Control Center > 3D Settings > Disable Morphological Filtering
Ler a resposta no contexto 👍 2

All Replies (2)

more options

Chosen Solution

In Firefox 4 and later Safe mode disables extensions and disables hardware acceleration.

  • Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"

If disabling hardware acceleration works then check if there is an update available for your graphics display driver.

If you have an ATI graphics display try to disable "Morphological Filtering" in the Catalyst display driver:

  • Catalyst Control Center > 3D Settings > Disable Morphological Filtering
more options

Thank you very much. Disabling hardware acceleration solved the problem.