Bug 353849

Summary: Find highlighting/selection uses its own (hardcoded?) color, which present usability issues
Product: [Applications] kmail2 Reporter: Michael D <nortexoid>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Michael D 2015-10-13 07:13:03 UTC 
I'm using the Breeze Dark color scheme (white text on black background). When I double click a word in a message, the background highlighting color is correct: white text with blue background. When I find a string in a message, the text is white but the background color is dark blue, which makes it near impossible to see. When I click "Highlight all matches" in the options, it gets worse: white text with bright yellow background! Basically illegible.

Is it possible to have the find colors adopt what is provided by the global color scheme? Or if they need to be hardcoded, hardcode both background *and* text color so the contrast comes out correct.

Reproducible: Always

Steps to Reproduce:
1. Change to global dark color scheme, like Breeze Dark.
2. Restart/open Kmail2
3. Open a message
4. Find a string

Actual Results:  
The found string has a custom highlighting color (perhaps just for background color).

Expected Results:  
The found string has the highlighting color as set by the global color scheme (for breeze dark: #3daee9)

Kmail2 5.0.1
Comment 1 Denis Kurz 2017-06-23 20:21:42 UTC 
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:54:00 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.