524094 - Windows colour settings not honored

Status: RESOLVED DUPLICATE of bug 435096

(Calendar :: General, defect)

Description

[BJ]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Lightning and Sunbird 0.9

I have configured Windows to show white text on a black background. I've done this through customising the appearance. The easiet way to replicate this is to select the Windows High Contrast Black colour scheme.

With this colour scheme text in certain parts of the Calandar window becomes invisible eg. the month in the top left pane, and text in the drop-down box below it.

This problem is geneally due to the background colour being hard coded as white instead of honour the Windows setting. This results in white text on a white background.

I shall attach a zip file with 2 screenshots. Thunderbird.bmp shows my screen colours as I like them to be. Lightning.bmp shows the problem.

As an additional request I would like to be able to configure Calander to display everything as white on black, as I can with Thunderbird. I don't wnat parts as white on black, and other parts as black on white.

Reproducible: Always

Steps to Reproduce:
1. Select Windows High Contrast Black colour scheme
2. Open Lightning or Sunbird
3.
Actual Results:  
You can't see some text as it's white on white

Expected Results:  
Displayed the text as white on a black background

This is the first time I've used Bugzilla. I can't see where to add my attachment. Perhaps I can add it afterwards...

Comment 1

[BJ]

Attachment: 2 screenshots. Lightining.bmp shows missing text

Comment 2

[Stefan Sitter [:ssitter]]

I can't open your attachment, neither as .zip or .bmp file. I therefore assume that you mean the same issue as reported in Bug 435096. Is this correct?

Comment 3

[BJ]

My attachment was a .zip file containing 2 .bmp files. I have just download it from this page by right clicking on the link and using Firefox's Save Link As. I have then successfully uncompressed the file with both WinZip and 7-zip.

Yes it does look like the same, or very similar, issue reported in bug 435096. Sorry i didn't spot that when I searched before adding a new report.

I do hope it can be addressed.