Closed Bug 65634 Opened 19 years ago Closed 19 years ago

Data in bottom area needs better colours

Categories

(Other Applications :: ChatZilla, defect, trivial)

defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mhearn, Assigned: rginda)

References

Details

Hi, I'm red/green colour blind and the darkslategray colour used in the data
area of ChatZilla is difficult for me to read. I think it should be changed to
white or the user be given an option, thanks -mike
Added access keyword and changed owner to aaronl
Assignee: rginda → aaronl
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: access
Hardware: PC → All
Which is the `data area'?

The log pane should use the user's default colors as set in the `Colors' panel 
of the prefs dialog. The list pane should use the normal platform styling for 
tree controls. And the comment pane should use the normal platform styling for 
a text entry control.
mpt: I'm sure the "bottom area" referred to is what chatzilla calls the status bar.

Keyser: this really isn't accessibility, it's just me making a poor color
choice.  ChatZilla is it's own project, and there is no reason for aaron to have
to hack chatzilla css files.

mhearn: for now, you can edit userChrome.css in the chrome subdirectory of your
profile.  Add something like:

.status-data {
    color: white !important;
}

If the file doesn't already exist, just create a new one.  You can also change
the colors of the output frame by modifying your userContent.css file in the
same subdirectory.  See the files <
http://lxr.mozilla.org/mozilla/source/extensions/irc/xul/skin/chatzilla.css> and
<http://lxr.mozilla.org/mozilla/source/extensions/irc/xul/skin/output-default.css>
for examples of what can be changed.

I'll make a more resonable default sooner or later.
Assignee: aaronl → rginda
Keywords: access
Depends on: 71468
superbug checked in, mass marking all dependents fixed.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: Core → Other Applications
You need to log in before you can comment on or make changes to this bug.