GNOME Bugzilla – Bug 710650
'Selected items' text is unreadable when using 'Windows Classic' theme
Last modified: 2018-04-15 00:18:49 UTC
I'm reporting this here because this behaviour is common across all GTK+ applications that I use, namely Wireshark, Inkscape, and GIMP. It also affects other applications that I can't confirm were made with GTK+: Opera 15+, VLC and Git-Gui. I use the 'Windows Classic' theme on all my Windows XP and 7 machines. Don't get me started on why. Most Windows applications work fine with this theme, but the ones listed above show this problem: list items (eg menu items) should have their text colour inverted when selected, but they don't (at least not always). Text that is normally black on a grey or white background should become white text on a dark blue background when selected. This works properly in all non-GTK+ applications. In GTK+ applications, the text in selected items stays black. If the default background colour (a dark blue) is used, the black text is basically unreadable. I've had to change the background colour for selected items to a different shade of blue to enable me to read this text. Hopefully I've posted this in the right place. It seems like a core GTK+ issue, although I can only confirm that it affects Windows applications. I looked for similar bug reports and didn't find any.
Created attachment 304229 [details] Blue background, black text animation When hovering the cursor in the menu the background becomes blue, but text color remains black, so hard to read it. Also for submenu items the graphics gets glitchy with the blue background new being drawn at the same time under the text as the rest of the blue background. There is also a "_" graphics glitch left of the submenu arrows. The bug is really annoying for me because i want to use the classic theme in Windows 7. And this bug makes me have a hard time just using the menus so i would like for it to have higher priority.
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new