Bug 318133

Summary: Certain elements of Konqueror's "Configure" window do not display correctly with some colour schemes
Product: [Applications] konqueror Reporter: Ben Morris <bugs>
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: 4.10.2   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshot demonstrating problem
Colour scheme used in screenshot

Description Ben Morris 2013-04-10 12:37:13 UTC 
In Konqueror's Configure window, File management -> Services and File management -> General -> Previews have large widgets that use "Window Text" colour text on a "View Background" backgrond.

Reproducible: Always

Steps to Reproduce:
1. Use System Settings to set "View Background" and "Window Text" to similar colours (or use the DarkDefault colour scheme from KDE-Look, currently third-highest-rated)
2. Open Konqueror's Configure dialog
3. Click on Services
Actual Results:  
The list of services is hard to read, as the names are drawn using the "Window Text" colour with a background colour of "View Background". This

Expected Results:  
Either use "Window Text" on "Window Background", or use "View Text" on "View background".
Comment 1 Ben Morris 2013-04-10 12:46:27 UTC 
Created attachment 78772 [details]
Screenshot demonstrating problem

Attached a screenshot of Konqueror's Configure window, with System Settings -> Colours also shown. System Settings has readable widgets because it uses View Text on a View Background, instead of Window Text on a View Background.
Comment 2 Ben Morris 2013-04-10 12:49:54 UTC 
Created attachment 78773 [details]
Colour scheme used in screenshot

Attached the colour scheme used in the screenshot; however the issue can also be reproduced using a popular scheme from KDE-Look: http://kde-look.org/content/show.php/DarkDefault?content=103454
Comment 3 Christoph Feck 2013-04-21 11:36:06 UTC 

*** This bug has been marked as a duplicate of bug 286459 ***