Closed Bug 455767 Opened 16 years ago Closed 16 years ago

Liberation Mono is not getting monospaced; other monospaced fonts are.

Categories

(Camino Graveyard :: Page Layout, defect)

PowerPC
macOS
defect
Not set
trivial

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: mlm, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

<html>
<head>
<title>Demo of Monospace Problem with Liberation Mono</title>
</head>

<body>
<p>
Following is a PRE tag with font-family "Liberation Mono".
</p>
<pre style="font-family: "Liberation Mono">
Note that the characters on these lines don't line up.
'"quotes are especially narrow.
IiMmJjLl
</pre>
<p>
This problem occurs with Liberation Mono, which I downloaded from
<a
href=""https://fedorahosted.org/releases/l/i/liberation-fonts/liberation-fonts-1.04.zip">
this link</a>, when using Camino 1.6.3.  It does not occur with Safari 3.1.2 or
Firefox 3.0.3.  I am not having problems with other monospaced fonts in Camino.
[Mac OS 10.5.4]
"https://fedorahosted.org/releases/l/i/liberation-fonts/liberation-fonts-1.04.zip"</p>
</body>
</html>


Reproducible: Always

Steps to Reproduce:
1.Create an html file from the text in "Details"
2.Open it.
3.Look at the character positioning in the PRE to see that it is wrong.
Actual Results:  
no monospacing

Expected Results:  
monospacing
Please use <http://pimpmycamino.com/parts/troubleshoot-camino> to test a nightly build from <http://caminobrowser.org/download/releases/nightly/>, which contains all the same font changes that went into Firefox 3.
It is a quirk (bug...) in Gecko 1.8.1. Both Camino 1.6.x and fx 2.0.0.x and older are affected. All works fine in Gecko 1.9 - Fx 3+, Camino 2.0a1pre+

You need to explicitly specify 'monospace' in the font-family rule, as in 
selector {font-family: 'Liberation Mono', monospace;}
Thanks philippe; closing WFM based on comment 2.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.