Closed Bug 159227 Opened 22 years ago Closed 22 years ago

Appearance Pref - Font Sizes Won't Stick

Categories

(Camino Graveyard :: Preferences, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: syrreg, Assigned: sfraser_bugs)

References

Details

Trying to change the Serif and Sans Serif to use Genevea 14 but Chimera keeps changing it to Geneve 16. Can not get it to use/remember Geneva 16.

Also, shouldn't we be able to choose to use Serif OR Sans Serif for display default?
->sfraser
Assignee: saari → sfraser
Blocks: 147975
Does this still happen in the Chimera 0.4 release?
Status: NEW → ASSIGNED
*** Bug 159271 has been marked as a duplicate of this bug. ***
You've probably already checked, but yes, it does occur with 0.4 official and it's also occuring with build 2002072505. I believe this problem has been there since 'Appearance' became a preference.
 
It will remember the font but not the size - it keeps changing the size back to 16.
*** Bug 160277 has been marked as a duplicate of this bug. ***
It seems it works only in tandem with the Cursive font size: you have to set all 
three (Serif, Sans-serif, Cursive) to the same size for it to work.
As a matter of fact, just changing the font size for Cursive causes the other
two to change to the same size as well.
The issue is that the prefs backend only stores one size for all proportional
fonts, so the last one you change will stick (approximately). The UI needs to be
redesigned.
*** Bug 162080 has been marked as a duplicate of this bug. ***
*** Bug 159272 has been marked as a duplicate of this bug. ***
QA Contact: winnie → sairuh
*** Bug 165078 has been marked as a duplicate of this bug. ***
*** Bug 168710 has been marked as a duplicate of this bug. ***
Redesigned fonts panel checked in, which fixes this.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
vrfy'd fixed with 2002.10.07.04. able to change font sizes.
Status: RESOLVED → VERIFIED
No longer blocks: 147975
You need to log in before you can comment on or make changes to this bug.