Closed
Bug 427360
Opened 17 years ago
Closed 17 years ago
CSS problem: dt {font-family: ... } is ignored
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: kwk, Unassigned)
Details
Attachments
(1 file)
|
242 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13
Within a <style> block within <head>, this has no effect:
dt {
font-family: monospace;
}
For dt, I was able to set other CSS elements such as:
font-style: italic;
margin-top: 0.5em;
as expected, but font-family is not processed.
Reproducible: Always
Steps to Reproduce:
<html>
<head>
<meta http-equiv="Content-Style-Type" content="text/css">
<style>
dt {
font-family: monospace;
}
</style>
</head>
<body>
<dl>
<dt> the DTs <dd> should be a monospace font
<dt> but <dd> they are not
</dl>
</body>
</html>
Actual Results:
The Defined Terms are in the default (sans-serif) font.
Expected Results:
They should be in a monospaced font.
|
Reporter | |
Comment 1•17 years ago
|
||
IE and Opera both process this correctly.
|
||
Comment 2•17 years ago
|
||
WFM on Mac (I tested Firefox 2.0.0.13 and Firefox trunk). The DTs are displayed in a monospace font for me.
|
||
Comment 3•17 years ago
|
||
|
||
Comment 4•17 years ago
|
||
wfm with Seamonkey trunk on vista
|
|
||
Comment 5•17 years ago
|
||
WFM, Firefox 2.0.0.13 and 3.0pre on both Windows XP and Linux.
Karl, can you reproduce the problem in Firefox 3.0b5 or later, with
a fresh profile?
http://kb.mozillazine.org/Profile_Manager
|
|
Reporter | |
Comment 6•17 years ago
|
||
I must apologize. I had forgotten one of my browser settings, namely, I do not "allow pages to choose their own fonts."
The page I have also uses <tt> and <pre>. I had gotten into a mindset that if those work, a CSS request for "font-family: monospace;" should also work.
No doubt, with the browser set as I had it, the CSS interpreter is simply ignoring all requests of the "font-" style while the main HTML interpreter continues to honor requests for monospace. Perhaps this behavior is somewhat inconsistent, but it is quite understandable.
Again, my apologies, folks. I have changed this "bug" to resolved, INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•