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

Font is messed up on Firefox 17.0

  • 109 பதிலளிப்புகள்
  • 169 இந்த பிரச்னைகள் உள்ளது
  • Last reply by Merecat

Just updated to FF17.0 and the fonts look awful, something like when the ClearType is enabled in Windows. I have ClearType disabled cause I hate the look of the fonts with it enabled, and now Firefox looks like it's all over it. Font is like bolded. What happened? Can I disable it somewhere in Firefox?

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Hey guys! Thanks to everyone who helped us in troubleshooting this. We are fairly certain it's an azure problem. There is a patch in the works and setting = False seems to work in the meantime. I don't know if the patch will be part of a chemspill or wait until 18. Thanks for your help and patience.

Happy Thanksgiving!

Read this answer in context 👍 17

All Replies (20)

Here are two screenshots to compare:



Nothing has changed in my settings either in Windows or in Firefox. Just simple update from 16.0.2 to 17.0.

Notice how awful the word "mozilla" looks in address bar.

Exactly the same problem. Can't find the option to turn off FF messing with fonts.

I noticed if I turn off the hardware acceleration in tools-options-advanced the fonts goes back to ordinary....but I shouldn't have to turn it off, I have a good graphic card so I want to have this options on

forhike மூலமாக திருத்தப்பட்டது

Well disabling HW accel. helps, but only partially. Firefox itself looks good, but fonts on certain sites now looks even more unreadable for me than before.

guniu மூலமாக திருத்தப்பட்டது

I have no problems with the fonts within the web sites, it looks as good as it did with FF 16.0.2 but I hope there is a solution because it looks terrible with the Hw enabled

It's actually just one site with custom font that I'm on that looks bad. All other sites look like they should.

I went back to 16.0.2...couldn't stand it :(

Note that on the Windows platform such issues on a web page can also be caused by Firefox placing all members of a font family in one group and selecting a member in that group based on CSS font rules.

You can use this extension to see which fonts are used for text that is selected (right-click context menu: Show fonts in selection).

You can do a font test to see if you can identify corrupted font(s).

My big issue is that firefox fonts on menu, bookmark toolbar etc looks really bad not on the sites. It looks all compact, blurry and thick. As guniu explained it looks like clear type is enabled...

I have disabled all plugins and extensions even reinstalled graphic drivers but the only thing that helps is to disable the HW acc so I went back to ff 16 for now,

forhike மூலமாக திருத்தப்பட்டது

This is a big usability issue for me, since I do a great deal of reading in firefox and hardware acceleration resulting in blurry text makes reading for more than a few minutes induce a very high level of eye strain.

Of course, turning off hardware acceleration is a temporary workaround, but it is far from ideal.

Note that using hardware acceleration means that Firefox uses the GPU instead of the CPU to do some (image) manipulations and that you may not notice any effect in Firefox if you disable hardware acceleration. If the GPU is used then specific operations like scrolling and font rendering that are performed internally by the graphics display driver can take more time (the GPU needs to do more if HA is enabled) and thus the graphics display card can respond less smoothly. There shouldn't be any reason to revert to an older Firefox version because of issues with hardware acceleration that can be fixed by disabling this feature.

See also:

But Cor-el, this is an issue that was introduced specifically in this update and did not exist with HW rendering prior, so that isn't really relevant here.

Why you moderators always respond like bots. Just read what we wrote, compare the screenshots I posted. There is something with font rendering in FF 17.0 that has changed since last version. And it looks like crap now.

guniu மூலமாக திருத்தப்பட்டது

Maybe source of this problem is hidden in this bug fix -

I have this problem too. Hate cleartype, so went back to FF 16.02. I think it's major issue that need to be fixed asap. Also noticed that FF safe mode don't have this problem. All this on Radeon 6950 with latest official drivers for Windows 7 SP1 64bit

I too, have this problem, wasn't like it prior to the 17 update, I even went to extreme lengths of removing all add-ons and even reset FF back to default the result is the same, fonts look like cleartype is enabled - like others cleartype looks bad on my system. The fonts are as they should be if starting in safe mode or deselecting hardware acceleration.

For now I've turned off hardware acceleration, but I shouldn't have to.

Huge sense of disappointment when I upgraded to FF17 and this happened. It affected the Win7 PC I use at work but did not affect the XP SP3 PC at home - why would this be? I use "Classic" theme on the work PC and do not have Cleartype (aka. Fuzzytype) enabled.

Hoping someone will post a fix here - have bookmarked this topic for now!

I used the trick of unticking the hardware acceleration option for now - seems to do the trick. Am I fighting a losing battle in my preference for pin-sharp font rendering? We had to update to Office 2010 here recently and I spent time changing back from fonts like "Segoe" to something that didn't blur the edges...  :-(

I reckon people with poor eyesight probably prefer "Cleartype" rendering because it "bulks out" the characters. I try to focus on the unresolvable blur it generates and get a headache! I understand the rationale for "Cleartype" but it's not for me. PC power these days should mean everything is easily and quickly customisable to individual preference, IMO.

I have this problem too guys. I noticed this problem wouldn't happen in Win 7 and for me only on Win 8: could you confirm that?

matthew_eli மூலமாக திருத்தப்பட்டது

On about:config, changing gfx.direct2d.disabled to true, resolve the problem.

a587626 மூலமாக திருத்தப்பட்டது

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6