Closed
Bug 29351
Opened 25 years ago
Closed 16 years ago
Setting a bad font in prefs should be ignored
Categories
(SeaMonkey :: Preferences, defect)
SeaMonkey
Preferences
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: pierre, Unassigned)
References
Details
(Keywords: helpwanted)
This bug comes out of bug 28883.
To reproduce:
- Enter these 2 lines in your prefs.js file:
user_pref("font.name.serif.x-western", "Times New Roman");
user_pref("font.name.serif.x-western", "QWEQWEQWE");
- Launch Mozilla and go the font prefs panel
==> Bug: the selected font defaults to the first font in the list.
Expected behavior:
We should ignore font names that don't exists (like "QWEQWEQWE"). The selected
font should stay the last known good font.
Changing component to Preferences
Assignee: neeti → matt
Component: Preferences: Backend → Preferences
Reporter | ||
Comment 2•25 years ago
|
||
Updated•25 years ago
|
Target Milestone: M16 → M18
Updated•24 years ago
|
Keywords: correctness
Updated•24 years ago
|
Keywords: helpwanted
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: samir_bugzilla → nobody
Priority: P3 → --
QA Contact: bugzilla → prefs
Target Milestone: Future → ---
Comment 6•16 years ago
|
||
This bug is being marked EXPIRED as it has seen no activity in a very long time.
If you think that the issue reported might still be relevant, please test with a recent release of SeaMonkey and if the problem persists feel free to re-open the report. Thank you.
http://www.seamonkey-project.org/
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → EXPIRED
Comment 7•16 years ago
|
||
Bulk reopening incorrectly expired bugs - no activity does not constitute no bug - these need proper checking.
Status: RESOLVED → REOPENED
Resolution: EXPIRED → ---
Comment 8•16 years ago
|
||
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b5pre) Gecko/20090516 SeaMonkey/2.0b1pre
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•