Closed
Bug 53402
Opened 25 years ago
Closed 25 years ago
Default Warpzilla fonts are not good selections.
Categories
(SeaMonkey :: Preferences, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: barrymarshall, Assigned: mkaply)
Details
Attachments
(1 file)
|
3.89 KB,
text/plain
|
Details |
Tested with Warpzilla nightly build 0919 on WSeB base with Scitech DD
on TP770X.
Warpzilla's basic font selection for both monospace and proportional
fonts is Arial. The problem is that Arial doesn't have a very good
Bold setting, so rending can be really bad. It's also a proportional
font, so it shouldn't be the default for monospace.
Netscape/2 4.61 uses Times Roman 10 for proportional and Courier 10 for
monospace.
| Assignee | ||
Comment 1•25 years ago
|
||
| Assignee | ||
Comment 2•25 years ago
|
||
This fix for this was to check in a new os2pref.js. While the fonts don't
actually work yet (almost) they are now defaulting correctly.
We took this bug as only applying to the default font in prefs since we have
other bugs for the font problems.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•25 years ago
|
||
Yeah, that's all I was driving at. I'll look at tonight's nightly to confirm.
| Assignee | ||
Comment 4•25 years ago
|
||
This won't be in the nightly I just uploaded. It should be in the next one.
Comment 5•25 years ago
|
||
adding verifyme since i don't have an os/2 machine to test on.
Keywords: verifyme
| Reporter | ||
Comment 6•25 years ago
|
||
Yup, everything is much better now. Closing.
Status: RESOLVED → CLOSED
Keywords: verifyme
Comment 7•25 years ago
|
||
resolved bugs should be marked verified, not closed. we should only close when
we've shipped. i know this sounds confusing --see bug 31738 for details.
Status: CLOSED → UNCONFIRMED
Resolution: FIXED → ---
Comment 8•25 years ago
|
||
re-resolving...
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•