Possible to make fonts in FF4 look less horrible?


Recommended Posts

I just uninstalled FF 3.6.15 and installed FF 4 (final) on Windows 7. The first thing I noticed when I loaded up a site was show bad the fonts look.

I've read that this is due to hardware acceleration. Can anyone tell me how to turn this off so the fonts can look normal again?

Thanks.

You can either use the above, or just tweak your ClearType settings. If you do a search in Windows 7 via the Start Menu for 'ClearType' it should give the option to adjust it to your preference, this will have an effect on the font appearance within both Firefox 4 and Internet Explorer 9, but will require you to restart the browser before taking effect I've noticed.

I think the same search can be completed in Windows Vista, while in Windows XP searching the web should find one of those PowerToys I think.

You can either use the above, or just tweak your ClearType settings. If you do a search in Windows 7 via the Start Menu for 'ClearType' it should give the option to adjust it to your preference, this will have an effect on the font appearance within both Firefox 4 and Internet Explorer 9, but will require you to restart the browser before taking effect I've noticed.

I think the same search can be completed in Windows Vista, while in Windows XP searching the web should find one of those PowerToys I think.

So i have to sacrifice quality of fonts everywhere else in the OS just so they look better in Firefox?

I think not!

Chrome also has hardware acceleration, but the fonts look fine. They should just fix it.

So i have to sacrifice quality of fonts everywhere else in the OS just so they look better in Firefox?

I think not!

Chrome also has hardware acceleration, but the fonts look fine. They should just fix it.

Not at all, in most cases it has barely any effect, maybe even a positive effect on the fonts around the OS. After tweaking my ClearType settings everything looked better universally.

And it isn't hardware acceleration, it's DirectWrite.

I just saw this in the Firefox Add-ons RSS feed:

Anti-Aliasing Tuner - https://addons.mozilla.org/en-US/firefox/addon/anti-aliasing-tuner/

That can make things look better because regardless of what company needs to fix what the font rendering by default is terrible.

on firefox, enter in the address bar "about:config"

search for "gfx.font_rendering.directwrite.enabled"

double click on it to change the value to "false"

restart firefox

That doesn't work. The key you're looking for is "gfx.direct2d.disabled", which you need to set to "true".

Also, I've tried the Windows ClearType tool and the Firefox extension mentioned. Neither of these work well either. They can make the fonts in Firefox look "different", but not necessarily better. The best you can do with these tools is make the fonts blurry, which is a different problem in itself. Additionally, the Windows ClearType tool will screw up the fonts in all other applications, making them noticeably worse.

The only real fix at the moment is to disable Direct2D in Firefox. Unfortunately, this will degrade performance in the browser. I don't care who is responsible for the bug, but I really hope someone will either fix it or create a work-around that allows us to keep Direct2D enabled.

That doesn't work. The key you're looking for is "gfx.direct2d.disabled", which you need to set to "true".

Also, I've tried the Windows ClearType tool and the Firefox extension mentioned. Neither of these work well either. They can make the fonts in Firefox look "different", but not necessarily better. The best you can do with these tools is make the fonts blurry, which is a different problem in itself. Additionally, the Windows ClearType tool will screw up the fonts in all other applications, making them noticeably worse.

The only real fix at the moment is to disable Direct2D in Firefox. Unfortunately, this will degrade performance in the browser. I don't care who is responsible for the bug, but I really hope someone will either fix it or create a work-around that allows us to keep Direct2D enabled.

Yeah it's ridiculous how much better things look with that set to true.

...

The only real fix at the moment is to disable Direct2D in Firefox. Unfortunately, this will degrade performance in the browser. I don't care who is responsible for the bug, but I really hope someone will either fix it or create a work-around that allows us to keep Direct2D enabled.

It's not a bug, it's how it's designed to render text (if it looked like GDI, that'd be a bug/limitation)

  • Like 1

It's not a bug, it's how it's designed to render text (if it looked like GDI, that'd be a bug/limitation)

No, what I'm seeing is definitely a bug. I refuse to believe that anyone in sober mind would actually design the font rendering to look like this. I can understand how some people would prefer blurry fonts like in OSX vs. sharp fonts like in Windows, but all of my text is faded and splotchy.

  • Like 1

No, what I'm seeing is definitely a bug. I refuse to believe that anyone in sober mind would actually design the font rendering to look like this. I can understand how some people would prefer blurry fonts like in OSX vs. sharp fonts like in Windows, but all of my text is faded and splotchy.

Show a screenshot then, you might actually be experiencing a bug.

Its actually an issue in Direct Write that also affects IE9 to some extent. MS needs to fix that, not Mozilla

Sadly, this is the attitude that Mozilla seem to be taking. For business purposes I have the following browsers installed & up to date on the computer;

Opera, IE, Firefox, Minefield, Chrome, Chromium, Maxthon.

Firefox (and minefield), IE, Chrome (and Chromium) are the only ones with hardware acceleration at the moment (I believe).

Want to know which are the only two that fonts look poor in? Firefox and Minefield.

It's not an MS problem, its a Mozilla problem, and the sooner they get their heads out of the sand and realise that, the better for them it will be.

That doesn't work. The key you're looking for is "gfx.direct2d.disabled", which you need to set to "true".

[...]

Thank you so much! I got a headache looking at the terrible font display in FF...

No, what I'm seeing is definitely a bug. I refuse to believe that anyone in sober mind would actually design the font rendering to look like this. I can understand how some people would prefer blurry fonts like in OSX vs. sharp fonts like in Windows, but all of my text is faded and splotchy.

I agree. In comparison to Chrome or other text displayed in Windows it looks absolutely terrible. It's actually hard to focus your eyes and read long articles this way. All the people I know who use FF4 complained about this.

Show a screenshot then, you might actually be experiencing a bug.

I'm curious to see this myself. Not calling BS or anything, but just not seeing anything wrong with the font rendering that some people are talking about. Everything's enabled, and it looks pretty good here.. renders a little differently maybe, but at least on my system it looks good and is comfortable to read.

Went and pulled up a couple of pages in FF4, the Chromium nightly from 2-3 days ago and IE9.. fonts render a little differently across the three but all look good.

Fonts doesn't look good here either, heard its a DirectWrite bug, there are a few threads about it over at mozillaZine, one is this: http://forums.mozillazine.org/viewtopic.php?f=23&t=2060933

And so far only "fix" seems to be turning hardware acceleration off, which i don't really like as i want to use that feature, but with the current look of fonts with that on, i have to.

this is odd.. the fonts looked horrible when i tried the betas and rc's and now that im on the final they seem normal. i havent do any windows updates either.

It's been improved, but there is still a difference

post-286512-0-52016200-1300806897.png

Top is FF4, bottom Chromium 12, both with hardware acceleration enabled

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!