993370 - Some UI components in Thunderbird don't obey the Windows 8.1 high-contrast mode

Status: RESOLVED DUPLICATE of bug 946595

(Thunderbird :: Theme, defect)

Description

[Kostadin Kolev]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140403132807

Steps to reproduce:

1. Right-click on an empty spot on the desktop, to invoke its context menu.
2. From the menu, choose "Personalize".
3. From the "Personalize" window that appears, click on "High-Contrast Black", in the list of available themes.
4. Launch Thunderbird.


Actual results:

The tree-view with the accounts and their folders, the toolbars, the headers pane for a selected/opened message, the almost whole address book - all they use a white background and a non-standard for the used Windows theme highlight/selection color. The used white background color, in combination with the theme's white text color, make the text in those components unreadable. The bug is a similar to a few others for Firefox: 975394, 975399, 986858.


Expected results:

Those components from the UI should completely obey the Windows high-contrast theme currently used and use its foreground, text and background colors.

Comment 1

[Richard Marti (:Paenglab)]

This will be solved in public TB 31 ESR release.

Comment 2

[Kostadin Kolev]

I'm now running a beta of Thunderbird 30 and the problem is fixed only partially. The things not fixed are: the toolbar (on the right of the menubar); the headers panel; the upper part of the message composer (where are the fields for the selection of the sender and for entering the recipients). At least those are the ones that I've noticed. We may include the "About" dialog, but may be that it is made that way by design.

Comment 3

[Richard Marti (:Paenglab)]

As I wrote in comment 1:

> This will be solved in public TB 31 ESR release.

TB 30 has still this issue and can't be fixed as the fix isn't in toolkit 30.

Comment 4

[Kostadin Kolev]

Aha, I understand. Because I updated to 29 beta some time ago and have noticed some fixes related to this, I've thought that all will be fixed at once, but it seams that I'll have to wait until v31 for that :). Thanks for the information.