Closed
Bug 321550
Opened 19 years ago
Closed 19 years ago
wrong font (proportional) is displayed for <pre> sections when using CSS + "always use my fonts"
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: alan.ezust, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051224 Debian/1.5.dfsg-3 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051224 Debian/1.5.dfsg-3 Firefox/1.5
Firefox stylesheet bug.
I am attaching a HTML page and a stylesheet.
This HTML page was generated with Docbook stylesheets.
I have UNCHECKED, the box that says
"allow pages to choose their own fonts, instead of my selections above".
So I want to see my favorite fonts on all pages.
The Docbook-generated HTML file has programlistings that look like this:
<pre class="programlisting">
program listing here
</pre>
If I view the page WITHOUT stylesheet, it properly has <pre>
sections in monospaced font. However, as soon as I use my CSS file
firefox renders all of my <pre class="programlistings"> in a regular font (not monospaced).
I am attaching the CSS file and the generated HTML file.
NOTE: this only happens when you have "always use my fonts" - if you
uncheck that, then it also renders <pre> sections in monospace correctly.
Reproducible: Always
Steps to Reproduce:
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Reporter | ||
Updated•19 years ago
|
Summary: wrong font is displayed when using CSS + "always use my fonts" → wrong font (proportional) is displayed for <pre> sections when using CSS + "always use my fonts"
Reporter | ||
Comment 3•19 years ago
|
||
This looks a lot like 298234, but that one was marked as invalid, and fixed?
Fixed in what version? I have seen the same problem since 1.0.7 but I am now using 1.5.
Reporter | ||
Comment 4•19 years ago
|
||
*** This bug has been marked as a duplicate of 79074 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•