If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

fonts in preferences/appearance not working

VERIFIED WORKSFORME

Status

SeaMonkey
Preferences
VERIFIED WORKSFORME
16 years ago
13 years ago

People

(Reporter: piersante sestini, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.0rc1) Gecko/20020418
BuildID:    2002041811

Choosing Edit/preferences/appearance/fonts the following appears:
XML Parsing Error: unclosed token
Location: chrome://communicator/content/pref/pref-fonts.xu
Line Number 287, Column 1

Also in preferences, "Privacy & security" does not expand when double clicking.
I get an error when trying a secure server.


Reproducible: Always
Steps to Reproduce:
1.edit->preferences->appearence->fonts
2.edit->preferences->Privacy&Security->try to expand
3.

Actual Results:  1)The following appears on the window on the right:
XML Parsing Error: unclosed token
Location: chrome://communicator/content/pref/pref-fonts.xu
Line Number 287, Column 1

2)The "plus" sign on the left change to a "minus", but nothing happens

Expected Results:  1) A choice of fonts should appear

2)The menu should expand to give choices about the topic

warp 4 Italian /FP15/ pentium100/ 64M RAM
have you installed 1.0RC1 over an okld mozilla version?

Comment 2

16 years ago
That's sure what it sounds like to me.

Please remove your entire Mozilla directory then reunzip RC1.

Comment 3

16 years ago
Reporter, please try our suggestions and if this continues to happen, reopen the 
bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
mass-verifying WorksForMe bugs.

reopen only if this bug is still a problem with a *recent trunk build*.

mail search string for bugspam: AchilleaMillefolium
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.