225047 - font-family: monospace doesn't work with "browser.display.use_document_fonts" set to 0

Status: VERIFIED DUPLICATE of bug 79074

(Core :: CSS Parsing and Computation, defect)

Description

[Isaac Hwak Han]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031105
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031105

Summary says all.

Reproducible: Always

Steps to Reproduce:
1. Uncheck "Allow documents to use other fonts" in Preferences/Appearance/Fonts
2. Open the testcase or URL



Expected Results:  
Elements with 'font-family: monospace' should display as monospaced text.

Comment 1

[Isaac Hwak Han]

Attachment: Testcase

Comment 2

[Felix Miata]

I'm using 1.6a on OS/2, and the only difference I see between allow or not is
that the last of the four lines switches between Andale Mono and Lucida Console.
Enabled, the first two are Lucida, the last two Andale, which is my monospace
pref. I don't understand why any of them display in Lucida. OTOH, I get exactly
what I ask for when styling a span (instead of using pre) with Lucida or Andale:
http://members.ij.net/mrmazda/auth/monospace-pt.html

Comment 3

[Boris Zbarsky [:bzbarsky]]

So what exactly is this UI option supposed to do?  What it does right now is to
allow only "-moz-fixed" and "none" as possible font-family values.  It will wipe
out both UA and user set font-families, in particular, not just author set ones.

Comment 4

[Simon Montagu :smontagu]

This overlaps a lot with bug 159440, if not exactly a dupe.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Yeah... This bug has a clearer description of the problem....

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

.

Comment 7

[Simon Montagu :smontagu]

... but maybe they are both duplicates of bug 79074?

Comment 8

[Boris Zbarsky [:bzbarsky]]

Yeah, there we go.

*** This bug has been marked as a duplicate of 79074 ***