Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Helvetica Neue and Arial rendering in bold after update to Fx13

  • 6 отговора
  • 32 имат този проблем
  • 3 изгледи
  • Последен отговор от nodleigh

more options

After my update to Fx13 Arial and Helvetica Neue are rendering as bold ( 700 ) instead of ( 400 ). This is only happening in Firefox, not in Chrome, Safari or even programs like Word or Photoshop.

I've already tried reinstalling the fonts but nothing seems to help.

After my update to Fx13 Arial and Helvetica Neue are rendering as bold ( 700 ) instead of ( 400 ). This is only happening in Firefox, not in Chrome, Safari or even programs like Word or Photoshop. I've already tried reinstalling the fonts but nothing seems to help.

Всички отговори (6)

more options

You can do a check for corrupted and duplicate fonts and other font issues:

more options

Same at my screen with FF 13 in German - so, because I'm tired having these problems I downgraded back to FF 12. Now everything is back to normal.

Thanks providing FF version 12.

The Helvetica and font problem is a very old one ...

more options

It has nothing to do with my fonts, they work perfectly fine in any other browser or program.

more options

This issue is still occurring for me in Firefox 14.01 for Mac. I'm on OSX 10.7.4, if that helps. IS there anyone at Mozilla aware of this/repairing this?

more options

Are more fonts affected?

Did you make sure that there aren't any duplicated or other font issues reported in Font Book?

You can use this extension to see which fonts are used for selected text.

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

more options

I use Suitcase Fusion to manage my fonts. There are no conflicts. I design web sites and test them in several browsers on several platforms/OS's. This is a Firefox-only issue.