280384 - Mozilla: courier > monospacer; IE 6.0: monospace > courier

Status: VERIFIED INCOMPLETE

(Firefox :: General, defect)

Description

[Ivan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When "font-family:courier" is specified in the style, it seems that Mozilla 
displays the text in courier font with the point size specified for serifs. This
results in big text, since courier 10 is bigger than times 10. When font-family
is "monospace" Mozilla honors monospace font size specified in options, and the
text looks fine.

IE has different behavior. When font family is "courier", it tries to find point
size, such that actual character height more or less matches that of serifs.
When font family is "monospace", it displays the text in courier font with the
reguilar point size, resulting in huge text.

This makes problematic writing a page with courier that looks good in both IE
and Mozilla. If I set font family "monospace", text is OK in Mozilla, but big in
IE. If I set family "courier", text is OK in IE, but huge in Mozilla.

If "courier" was treated the same as monospace, I could just set font faily to
"courier" and leave it alone.

Reproducible: Always

Steps to Reproduce:
1. Go to the URL in Mozilla. See text
2. Go to the URL in IE. See text


Actual Results:  
Handlnig of font families is exact opposite in the two browsers

Expected Results:  
Handle font families should be as compatible as possible

Comment 1

[Ivan]

Attachment: Screenshot

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Ivan]

The bug is still there (Firefox 1.0.7)

Comment 4

[Samuel Sidler (old account; do not CC)]

Ivan, can you please attach a testcase to this bug. If you're not seeing this bug anymore, please let me know so we can close it as "works for me".

Comment 5

[Samuel Sidler (old account; do not CC)]

Closing this bug as INCOMPLETE. Without more information, we can't move ahead. If you can reproduce this using Firefox 2.0.0.3 with a new profile and can provide a testcase or more information on how to reproduce, please comment in the bug.