Bug 146907 - Firefox displays a gray background (system default) - should be white as most websites expect this
Firefox displays a gray background (system default) - should be white as most...
Status: CLOSED DUPLICATE of bug 143423
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-02-02 12:36 EST by Kyrre Ness Sjøbæk
Modified: 2007-11-30 17:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-13 15:07:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kyrre Ness Sjøbæk 2005-02-02 12:36:40 EST
Description of problem:
Firefox currently uses a gray background for webpages which does not
explicitly set their background colour. This is not what most modern
webpages and users normally expect - they expect white.

This makes a lot of webpages look broken in fedora rawhide firefox

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

How reproducible:
Every time. Leaves nice, white "frames" around buttons (etc) on a lot
of pages.

Steps to Reproduce:
1. Open a webpage that look broken if you change the background colour
(f. ex. phpBB forums such as the one on forum.hardware.no)
2. Look!
3. Not pretty
  
Actual results:
Gray background

Expected results:
White background when not explicitly set

Additional info:
Thread in devel-list at:
https://www.redhat.com/archives/fedora-devel-list/2005-January/msg01879.html
Comment 1 Rex Dieter 2005-02-02 12:44:47 EST
Count me as one user who prefers the existing "use system colors" 
default.
Comment 2 Christopher Aillon 2005-02-13 15:07:55 EST

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

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