Open Bug 554963 Opened 16 years ago Updated 3 years ago

view source on message always shows black on white - accessibility

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect

Tracking

(Not tracked)

People

(Reporter: joshudson, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3 The view source window respects neither system colors nor mail colors but always shows white on black. Reproducible: Always Steps to Reproduce: 1. Select any message 2. View source Actual Results: The background is white, the text is black. Expected Results: The content window uses the same colors as "display mail" under tools/options/display/colors. I have extreme eye sensitivity requiring me to set background colors to black.
Can someone sighted confirm this bug? This is obviously a problem for visually impaired people who might need different contrasts or inverted colors to be able to read the text.
(In reply to comment #1) > Can someone sighted confirm this bug? This is obviously a problem for visually > impaired people who might need different contrasts or inverted colors to be > able to read the text. confirming. Marco shall this be blocking some of the accessibility bugs ?
Status: UNCONFIRMED → NEW
Component: General → Mail Window Front End
Ever confirmed: true
QA Contact: general → front-end
(In reply to comment #2) > (In reply to comment #1) > > Can someone sighted confirm this bug? This is obviously a problem for visually > > impaired people who might need different contrasts or inverted colors to be > > able to read the text. > confirming. Marco shall this be blocking some of the accessibility bugs ? It shall. ;)
Blocks: 343205
Observed fixed 3.1.11 on Windows 7.
Keywords: access
No longer blocks: 343205
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.