After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618325 - Unfocused GtkTreeView loses highlighting in MS Windows theme engine
Unfocused GtkTreeView loses highlighting in MS Windows theme engine
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.16.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-05-10 23:30 UTC by Gerald Combs
Modified: 2018-02-10 03:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Gerald Combs 2010-05-10 23:30:47 UTC 
It looks like the MS Windows theme engine isn't drawing insensitive GtkTreeView rows correctly. Steps to reproduce:

  Do the following with the MS Windows theme engine enabled and disabled:

  1. Select an item in a GtkTreeView so that a row is highlighted.
  2. Select another widget so that focus is taken away from the
     GtkTreeView.

If the MS Windows theme is disabled, the unfocused selected row is drawn with a gray (insensitive?) background. If the engine is enabled it is drawn with a white background. I've been able to confirm this with gtk-demo and Wireshark.

This appears to be the underlying cause of https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445
Comment 1 Martin Schlemmer 2011-11-28 12:41:39 UTC 
From that bug, it was with 2.18.x, which did not have the fixes from bug #598299. As far as I know, it was pushed to 2.22.x and later only, and personally I have not used anything myself on Win32 besides 2.16, as the later ones all had some rendering/backend issues.

2.24.8 looks promising though, so can you try on that perhaps? Over here the TreeView (Win7) works as expected with 2.24.8.
Comment 2 Matthias Clasen 2018-02-10 03:44:30 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.