1291186 - Tagged Email: highlighting does not change to Tag color when tagged mail es selected, text more or less unreadable.

Status: UNCONFIRMED

(SeaMonkey :: OS Integration, defect)

Description

[Christian Franke]

Attachment: Sample screenshot

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
Build ID: 20160120202951

Steps to reproduce:

1. Upgrade to Windows 10
2. Open MailNews
3. Select a mail in Thread Pane
4. Type '1' to tag the mail as "Important" (red)



Actual results:

Selected line is hardly readable:
text color: white, background color: light blue
(regardless of tag color)



Expected results:

Color combination shall be more readable and should include the tag color.


The problem could be reproduced on several machines which were upgraded to Windows 10 recently. It is SM specific, TB is not affected. The problem did not occur on Windows 7. 

Workaround: deselect line (red, white) or deselect pane (red, grey)

Comment 1

[Rainer Bielefeld]

In Thread Pane on WIN7 (and Ubuntu) when I move highlighting by downarrow one by one: for tagged emails the highlighting background color changes from somehow light grey to the Tag-color, and text color changes to white. 
Due to reporter's screenshot the missing background-color-change is reason for the problem.

Comment 2

[Rainer Bielefeld]

@reporter:
I asked at mozilla.support.seamonkey and got an answer:
"Unable to reproduce with Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0 SeaMonkey/2.44"

a) May be there is some particular thing common with all the PC you tested?
b) Also reproducible in Safe Mode without add-ons or newly created user profile?

Comment 3

[Christian Franke]

a) Windows 10 x64 Pro DE with SM 2.40 en_US or DE. Graphics hardware vary (AMD, NV, ...). SM 2.44 not tested yet because 2.40 is still advertised as current release.

b) Sorry, forgot to mention: Yes, same result with new profile and no extensions/plugins enabled.

Further testing shows that only "Default Theme" is affected. Switching to "Modern" fixes the problem. Possibly some subtle difference between Win7 and Win10 which breaks this (and only this) in Default Theme.

Comment 4

[Christian Franke]

The root of the problem might be in the file chrome/toolkit/skin/classic/global/tree.css (from omni.ja):

Unlike modern/global/tree.css, the classic variant contains OS specific settings for "windows-xp ... -vista -win7 -win8" but not for win10.

Unfortunately selecting Win8 compatibility in the shortcut to seamonkey.exe has no effect, likely because its manifest indicates compatibility with Windows 10.

After removing the Win10 compatibility ID {8e0f...5a9a} from the manifest with a hex editor, the problem does no longer occur.