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 743683 - Using GtkComboBox-appears-as-list: 1 breaks mouse control
Using GtkComboBox-appears-as-list: 1 breaks mouse control
Status: RESOLVED DUPLICATE of bug 776793
Product: gtk+
Classification: Platform
Component: Widget: GtkComboBox
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-01-29 10:31 UTC by Vojtech Trefny
Modified: 2017-08-28 20:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vojtech Trefny 2015-01-29 10:31:40 UTC 
Using CSS style "-GtkComboBox-appears-as-list: 1" for GtkComboBox makes the box imposible to control with mouse inside Gtk.Dialog (works with keyboard navigation).

Steps to reproduce:
1. Run this simple example: https://gist.github.com/vojtechtrefny/ed5ac485585484483b6c
2. Click on "Open dialog"
3. Try to select something from the combo box using your mouse.

Currently for example oxygen-gtk theme sets appears-as-list to 1 making some GTK3 application unusable in KDE. But the problem appears with all themes (the example code above "works" in pure GNOME too).

KDE bug: https://bugs.kde.org/show_bug.cgi?id=343478
Comment 1 Ian Puleston 2017-01-03 07:03:08 UTC 
It looks like this is now fixed in GTK 3.22.4. I am seeing a problem with the same symptoms (bug 776793) and I tried running the app attached here to see if it is the same problem. What I found was that on my Fedora 23 system with GTK 3.18.9 the app shows the problem as described, but in Windows / msys2 with GTK 3.22.4 it does not happen and the "appears-as-list" combo works fine.

And note that the problem reported in bug 776793 has the same symptoms but that one does still happen in Windows / msys2 with GTK 3.22.4 where this does not, hence it is not the same cause.
Comment 2 Daniel Boles 2017-08-24 09:08:51 UTC 
Vojtech, do you stil get the reported problem in latest GTK+ 3.22? If so, does applying Ian's patch from the other bug resolve it?
Comment 3 Daniel Boles 2017-08-28 20:30:47 UTC 
Yup, same cause, and fixed in gtk-3-22.

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