Closed
Bug 26486
Opened 25 years ago
Closed 24 years ago
Can't choose default font when page doesn't specify one
Categories
(SeaMonkey :: Preferences, defect, P3)
SeaMonkey
Preferences
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: gehlhaar, Assigned: matt)
Details
(Whiteboard: WORKSFORME?)
Currently, you can't choose a font to be used when the page doesn't
specify one. The default is locked in as "serif", and I'd much
prefer "sans-serif". NS4.x lets me set this.
I assume this is cross-platform, but I can only test the Mac.
Comment 1•25 years ago
|
||
Hi. I'm not sure exactly what you mean. You either have a pre-M13 build, which
doesn't have the new font preferences panel, which lets you choose all kinds of
fonts for all kinds of occasions. Or you do have M13 and are saying that what
you choose there doesn't actually get remembered. That is bug 24830. Please
reopen and explain if I've misunderstood.
*** This bug has been marked as a duplicate of 24830 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Neither of those is what I mean. I should have been more specific.
Sorry.
Take the following HTML:
<p>
What font is this in?
<p>
<FONT FACE="sans-serif">This is in sans-serif</FONT>
<p>
<FONT FACE="serif">This is in serif</FONT>
Now, the Mozilla font prefs lets you select what font you want
to use if "serif" or "sans-serif" or whatever is specified. It
*doesn't* let you choose the font to use when *nothing* is
specified, which is the case for the vast majority of web pages
out there (including the Mozilla home page). The default is "serif".
I want to be able to change that default to "sans-serif" or whatever.
NS4 uses a different font prefs UI: given the encoding, you choose
what font you want for variable-width and what font you want for
fixed-width. That way, I can select the default font if none is
specified. I think that the Mozilla UI is better, in that it allows
finer-grained control, but it's lacking that one feature that I'd
really really like.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 3•25 years ago
|
||
Putting erik & myself on CC list. Platform/OS = All.
OS: Mac System 8.5 → All
Hardware: Macintosh → All
Comment 4•25 years ago
|
||
The back-end does have a way to set this:
user_pref("font.default", "sans-serif");
The problem is that the UI does not support this yet.
Eric,
Should we add a preference for this in M15?
Target Milestone: M15
Comment 6•25 years ago
|
||
I'd like to see it in the UI in M14, but I have no idea what your work-load
and priorities are like. Your manager's call.
Bulk move of all Pref UI component bugs to new Preferences component. Pref UI
component will be deleted.
Component: Pref UI → Preferences
Silly me, but isn't this done? It's in the current UI, and seems
to work fine.
Updated•25 years ago
|
Target Milestone: M16 → M18
Comment 11•24 years ago
|
||
The UI is there now. Due to other bugs I cannot check if it is actually
working or not.
Whiteboard: WORKSFORME?
Comment 12•24 years ago
|
||
Resolving this as WORKSFORME.
The UI allows you to select a default font (per language encoding) for Serif
and Sans Serif. Underneath these dropdown menus, there are 2 radio buttons
for "Default Type:". So if you want Arial as the default font, you
set Sans Serif to Arial and then check the Sans Serif radio button.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 13•23 years ago
|
||
mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".
if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:
a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]
b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•