Closed Bug 450098 Opened 16 years ago Closed 16 years ago

With user-set text and background colors, some form controls honor the background color but not the text color

Categories

(Firefox :: Settings UI, defect)

3.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 437366

People

(Reporter: Guido102005, Unassigned)

Details

(Keywords: access)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

Changing background color indeed change the background color of every element in the page, including listboxes, conmmand buttons and textboxes (like this one).
On the other hand, these elements are not affected by changes in text color, so if I choose a light text (white, yellow, ...) on black background, all the listboxes, conmmand buttons and textboxes ends becoming completely black and, so, unreadables!


Reproducible: Always

Steps to Reproduce:
1.set text color to yellow
2.set background color to black
3.uncheck both the checkboxes in Tools->Options->Colors (use system colors and allow the page to choose his own colors)
4.go to any page like google, ebay, ...
Actual Results:  
all the listboxes, conmmand buttons and textboxes in the page become completely black and unreadables!

Expected Results:  
1. The text of all the listboxes, conmmand buttons and textboxes should become of the selected color;
2. or, if this is not possible, at least, the background color of these elements should remain unchanged.

I've tried also to use Accessibar, but it doesn't helps.
Version: unspecified → 3.0 Branch
Keywords: access
Summary: changing text color doesn't affect some elements who are instead affected by changing background color → With user-set text and background colors, some form controls honor the background color but not the text color
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.