Bug 241813 - Incorrect CSS font designation for pre in bugzilla.css
Summary: Incorrect CSS font designation for pre in bugzilla.css
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: devel
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-30 20:11 UTC by Ray Van Dolson
Modified: 2013-06-24 02:52 UTC (History)
0 users

Fixed In Version: 2.18
Clone Of:
Environment:
Last Closed: 2007-05-30 20:20:11 UTC
Embargoed:


Attachments (Terms of Use)
Patch that fixes bugzilla.css for me. (252 bytes, patch)
2007-05-30 20:11 UTC, Ray Van Dolson
no flags Details | Diff

Description Ray Van Dolson 2007-05-30 20:11:39 UTC
Description of problem:
On line 51 in https://bugzilla.redhat.com/bugzilla/css/bugzilla.css, the 
font-family is defined as "mono".

On my various Firefox browsers under Windows and Fedora Core 6 (using both the 
Firefox RPM and Gran Pariso), all comments under RH Bugzilla bugs show up using
a variable-width font vs a fixed width font.

If I save the CSS locally and change "mono" to "monospace", everything looks 
correct.

However, using IE or galeon, the comments correctly use a fixed-width font even 
though font-family is set at "mono".

Should this be set to "monospace" to be valid instead of just "mono" ?

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. View Bugzilla bug at bugzilla.redhat.com in Firefox on Win/Linux
2. Observe comments
  
Actual results:
Font is variable width

Expected results:
Font is fixed width

Additional info:
Other users I discussed this with on #fedora did not all have this same issue.  
However, they felt that using "monospace" was correct and "mono" was not 
regardless.

Comment 1 Ray Van Dolson 2007-05-30 20:11:39 UTC
Created attachment 155744 [details]
Patch that fixes bugzilla.css for me.


Note You need to log in before you can comment on or make changes to this bug.