Closed Bug 186025 Opened 22 years ago Closed 22 years ago

letters on menues /forms are badly spaced (impossible to read)

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
FreeBSD
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: till, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3a) Gecko/20021218 Phoenix/0.5
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3a) Gecko/20021218 Phoenix/0.5

sometimes the spacing is so bad that the order of letters is switched, e.g. 
the  menu "View" reads "_iVew" (i and V overlap a bit)
the http address for this site is impossible to decipher  without copying
and pasting it into some terminal
It seems that the spacing of the letter i is completely off.

Reproducible: Always

Steps to Reproduce:
1.start phoenix
2.
3.

Actual Results:  
get an illegible toolbar

Expected Results:  
get a useable toolbar

mozilla/beonex works fine
Is this a default install without a theme?  What WindowManager are you using?  
INSTALL: default install without themes from the FreeBSD ports collection.

WINDOWMANAGERS: blackbox, hackedbox, ratpoison, fluxbox, icewm give the same result

Other Browsers: Mozilla 0.9-1.2 and Beonex 0.8 worked/work fine

I am rebuilding phoenix without anti-aliasing now and post result by tomorrow. 
phoenix doesn't have any freeBSD hackers so this bug is unlikely to see any
action unless some freeBSD person steps up to investigate and fix
there are two short term solutions:
1) disabling anti-aliasing (build using option WITHOUT_XFT)
2) removing at least the following fonts (there may be others) from the fontpath
in the X configuration file (XF86Config or XF86Config-4)

    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
  
I'll try to contact the maintainer of the phoenix port
Phoenix builds don't enable xft. This is not our bug.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
verified invalid 2004-01-10
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.