Bug#445385: Unreadable web page buttons with white-on-black GTK theme

[Trent W. Buck]

On Fri, Oct 05, 2007 at 06:30:22PM +0200, Mike Hommey wrote:
> On Fri, Oct 05, 2007 at 11:15:18PM +1000, Trent W. Buck wrote:
> > Package: libwebkitgdk0d
> > Version: 0~svn25144-2
> > Severity: normal
> > File: /usr/lib/WebKit/GdkLauncher
> > 
> > With a white-on-black GTK theme, buttons on web pages (e.g. the
> > "Google Search" button on google.com) become black-on-black, and
> > unreadable.
> 
> Would you have an example of such a theme ?

Sorry, here is my .gtkrc-2.0 (attached).
-------------- next part --------------
#### -*- conf -*-
#### http://library.gnome.org/devel/gtk/unstable/GtkSettings.html
#### Engine settings in /usr/share/gtk-engines/*.xml

gtk-cursor-theme-name = "DMZ-Black"
gtk-toolbar-style = GTK_TOOLBAR_BOTH_HORIZ
gtk-scrolled-window-placement = GTK_CORNER_TOP_RIGHT
gtk-enable-animations = 0
## Broken: can't close windows (steals C-w) and only implements the
## most superficial Emacs behavious anyway -- not even C-SPC!
# gtk-key-theme-name = "Emacs"
## Broken: forces the use of HC pngs for some icons.
# gtk-theme-name = "HighContrastInverse"
gtk-icon-theme-name = "HighContrast-SVG"

## Gtk-color-scheme exists so that you can customize a theme's color
## scheme without understanding the intricacies of the theme itself.
## If you set gtk-color-scheme in gnome-settings-daemon, this works.
## Just setting it and gtk-theme-name in this file DOES NOT work,
## because symbolic references are resolved at parse time -- that is,
## they only work within the file in which they occur, not in included
## files or gtk-theme-name files.
##
## What to do?  You can 1) run gnome-settings-daemon; 2) copy the
## theme you want into ~/.themes/twb and change the ONE LINE that sets
## gtk-color-scheme, then set gtk-theme-name to "twb".  I have done a
## variant of latter, copy-and-pasting a stripped-down theme in below.
gtk-color-scheme = "fg_color: white
bg_color: black
text_color: white
base_color: black
selected_fg_color: white
selected_bg_color: grey20
tooltip_fg_color: white
tooltip_bg_color: black"

## Symbolic names were introduced in 2.10, so on older hosts you'll
## see default colors and get a parse error warning on stderr.
## Similarly, if libindustrial.so isn't available, you'll get the
## default engine, Raleigh.
##
## Note that I'm using the old Industrial and High Contrast engines.
## That's because none of the other engines seem able to cope with a
## completely black background -- you end up with a fantastically
## useless amount of black-on-black borders and checkboxes.
style "twb" {
  engine "hcengine" { edge_thickness = 1 }
  engine "industrial" { contrast = 0.5 }
  base[INSENSITIVE] = @base_color
  bg[INSENSITIVE]   = @bg_color
  fg[INSENSITIVE]   = @fg_color
  text[INSENSITIVE] = @text_color
  base[NORMAL]      = @base_color
  bg[NORMAL]        = @bg_color
  fg[NORMAL]        = @fg_color
  text[NORMAL]      = @text_color
  base[ACTIVE]      = @base_color
  bg[ACTIVE]        = @bg_color
  fg[ACTIVE]        = @fg_color
  text[ACTIVE]      = @text_color
  base[SELECTED]    = @selected_bg_color
  bg[SELECTED]      = @selected_bg_color
  fg[SELECTED]      = @selected_fg_color
  text[SELECTED]    = @selected_fg_color
  base[PRELIGHT]    = @selected_bg_color
  bg[PRELIGHT]      = @selected_bg_color
  fg[PRELIGHT]      = @selected_fg_color
  text[PRELIGHT]    = @selected_fg_color
}
widget_class "*" style "twb"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-webkit-maintainers/attachments/20071006/507d33b6/attachment.pgp