GNOME Bugzilla – Bug 707786
Collapsed Gtk combo boxes no longer emit accessible selection-changed events
Last modified: 2018-05-02 15:48:06 UTC
Created attachment 254505 [details] event listener Steps to reproduce: 1. Launch the gtk3-demo combo boxes demo 2. Launch the attached event listener in a terminal 3. Tab to a combo box and then use Up/Down to change the selected item while the combo box remains collapsed Expected results: object:selection-changed events would be printed by the listener Actual results: object:selection-changed events would be printed by the listener Impact: Orca no longer presents the newly-selected item in collapsed combo boxes. The commit which introduced this change: https://git.gnome.org/browse/gtk+/commit/?id=7cecc8e524f9ac3825622e10f8a98f5e01ac4727
Combo-boxes is a really common widget. This regression deserves a 3.10 target too.
Just-before-code-freeze ping?
commit 45d896a6b5c144c7bdf956f255f59c1108dc258a Author: Benjamin Otte <otte@redhat.com> Date: Mon Sep 16 15:36:07 2013 +0200 Revert "a11y: Remove AtkSelection implementation from combobox" This reverts commit 7cecc8e524f9ac3825622e10f8a98f5e01ac4727. It is impossible to use the selection object of the menu while it is collapsed (collapsed menus deselect everything for a start), so even though the original patch was correct, the followup issues are too big to solve this quickly to a release. Leaving the bug open so we don't forget about this.
moving off blocker list
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.
Setting the status to NEW because of what Benjamin said in comment 3. I myself don't have a problem with it being closed.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/446.