261306 - yellow/blue backgrounds in prefs are unreadable if OS text color is white

Status: RESOLVED INCOMPLETE

(Firefox :: Settings UI, defect)

Description

[Chris Petersen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Galeon/1.3.14
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Galeon/1.3.14

The light-colored backgrounds (blue behind the section, and yellow behind
privacy options) in the latest firefox (and thunderbird) prefs result in
unreadable text if the default OS text color is light (mine is near-white, since
my background colors are near-black). 

Reproducible: Always
Steps to Reproduce:
open prefs



If you're going to hard-code colors in, PLEASE make sure that you hard-code BOTH
foreground AND background colors, or those of us who use nonstandard colors
(light-on-dark reduces eye strain because it's easier for the eyes to pick out
light shapes against a dark background) suffer a great annoyance.

Thunderbird has several other locations where you hard-code background colors
(like enigmail notices), so someone should probably go through both apps and
make sure that the colors are configured properly.

Comment 1

[Gavin Stokes]

I heartily agree; the inverse video color scheme (black text on white
background) is a vestige of the failed idea that the screen should emulate a
piece of paper.  Well, paper doesn't emit light.  Running three electron guns
full blast in your face all day to create a glaring white background is dumb.

This bug shouldn't be allowed to stand.  Vote sumbitted.

Oddly, I don't see this problem in the Windows release version.

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

[Chris Petersen]

This is still an issue in thunderbird...  I checked firefox and it looks ok on
my box now, but this may be entirely because I've gone in and manually edited my
chrome files to fix a lot of this stuff.  Either way, still needs to be fixed.

Comment 4

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change