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!

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Thin Font in Windows XP with ClearType switched off

  • 6 відповідей
  • 2 мають цю проблему
  • 1 перегляд
  • Остання відповідь від eXalted

more options

This is a problem which began with some of the newer versions of Firefox ( I don't remember which one exactly ). The fonts of some of the pages are rendered too thin. However they are rendered as they would in Chrome. I noticed that the problem is happening when I have the Windows XP ClearType font option is switched off. However I can't stand using the ClearType option in Windows - it makes text harder to read for me. Is there a way to fix this problem for Firefox. It wasn't present in the older versions, why has it appeared now?

Here's a screenshot of the problem: http://oi42.tinypic.com/104rkpk.jpg

I tried these solutions:

1. Starting Firefox in Safe Mode.

2. Disabling Hardware Acceleration in Firefox.

3. Toggling gfx.direct2d.disabled and gfx.direct2d.force-enabled to true.

And still the problem remains. Any help will be greatly appreciated.

This is a problem which began with some of the newer versions of Firefox ( I don't remember which one exactly ). The fonts of some of the pages are rendered too thin. However they are rendered as they would in Chrome. I noticed that the problem is happening when I have the Windows XP <b>ClearType</b> font option is switched off. However I can't stand using the ClearType option in Windows - it makes text harder to read for me. Is there a way to fix this problem for Firefox. It wasn't present in the older versions, why has it appeared now? Here's a screenshot of the problem: http://oi42.tinypic.com/104rkpk.jpg I tried these solutions: 1. Starting Firefox in <b>Safe Mode</b>. 2. Disabling <b>Hardware Acceleration</b> in Firefox. 3. Toggling <b>gfx.direct2d.disabled</b> and <b>gfx.direct2d.force-enabled</b> to <i>true</i>. And still the problem remains. Any help will be greatly appreciated.

Змінено eXalted

Усі відповіді (6)

more options

Hello eXalted, you said : ClearType font option is switched off

you mean you have select the "Standard" option ? in the box Use the following method to smooth edges of screen fonts

if yes, try to uncheck the Use the following method to smooth edges of screen fonts [ ] (leave it without selection), and check firefox again.


thank you

Змінено ideato

more options

Thanks for the reply. Yes, I selected Standard, but when I unchecked the option completely, it made them worse.

Here's a screenshot: http://oi40.tinypic.com/348q2bq.jpg

Chrome on the other hand is continuing to display them normally.

I would really appreciate any further help :(

Змінено eXalted

more options

Try to tune ClearType with the Windows ClearType Tuner to see if you can have it switched on:

Do you have an LCD screen or a CRT type display?

ClearType usually doesn't work well with CRT type displays, but should work with LCD displays.

more options

Yeah, I installed it and tried different settings but I just can't get my eyes around it.

It just seems strange that Firefox stopped supporting normal font visualization on systems without ClearType..

more options

Hello,

It just seems strange that Firefox stopped supporting normal font visualization on systems without ClearType..

in my xp with uncheck Use the following method to smooth edges of screen fonts [ ] it is perfect, i have no problem, the problem is somewhere else, but where ?

check if you have in Display > Settings > color quality > Highest 32-bit


thanks again

more options

Nope, the problem is still here. I'm on 32-bit, always were.

Very strange, how this problem suddenly appeared after some update.