Bug 148112

Summary: inverted YaST colors are inconsistent
Product: [openSUSE] SUSE Linux 10.1 Reporter: Christian Boltz <suse-beta>
Component: InstallationAssignee: Stefan Hundhammer <shundhammer>
Status: RESOLVED WONTFIX QA Contact: Klaus Kämpf <kkaempf>
Severity: Minor    
Priority: P5 - None    
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screenshot: proposal
Screenshot: update options

Description Christian Boltz 2006-02-03 20:22:08 UTC 
While playing around with my keyboard ;-)  I found the feature to invert the YaST2 colors while installation (Shift-F4) for having a high contrast.

Unfortunately, the coloring is inconsistent - many items seem to have the colors hardcoded. Even worse, some items have only the background color hardcoded, resulting in a turquoise font on grey background :-(

I'll attach two screenshots that show the problem.
Comment 1 Christian Boltz 2006-02-03 20:23:01 UTC 
Created attachment 66414 [details]
Screenshot: proposal
Comment 2 Christian Boltz 2006-02-03 20:24:49 UTC 
Created attachment 66415 [details]
Screenshot: update options

* Please note the help text color.
* The checkboxes are nearly invisible.
Comment 3 Stefan Hundhammer 2006-04-03 10:07:26 UTC 
later
Comment 4 Stephan Kulow 2008-06-25 09:35:19 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:37:20 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:42:06 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 7 Stephan Kulow 2008-06-25 09:53:30 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(