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 560826 - When an item in a combobox looses its Selected state, it should be notified.
When an item in a combobox looses its Selected state, it should be notified.
Status: RESOLVED DUPLICATE of bug 711397
Product: gtk+
Classification: Platform
Component: Accessibility
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-11-14 17:36 UTC by Andrés G. Aragoneses (IRC: knocte)
Modified: 2018-02-10 16:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrés G. Aragoneses (IRC: knocte) 2008-11-14 17:36:00 UTC
Please describe the problem:
When using a combobox, if you inspect one of the items with accerciser, you can see that the new state SELECTED gets added if you select it. However, when you deselect it, the SELECTED state doesn't disappear.

Steps to reproduce:
1. Have a combobox with options A, B, C.
2. Run accerciser, select your app, expand the tree until you find the menuitem A and select it.
3. Go to InterfaceViewer in accerciser, open Accessible: in the States list you don't see the SELECTED state.
4. Go to your app and select the value A with the mouse (the new state SELECTED appears in accerciser).
5. Select the item B.

Actual results:
The state SELECTED is still on the list of states of menuitem A.

Expected results:
The state SELECTED should disappear.

Does this happen every time?
Yes.

Other information:
I'm using Gtk and accerciser versions that come with OpenSUSE 11.0.
Comment 1 Matthias Clasen 2018-02-10 04:58:40 UTC
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.
Comment 2 Joanmarie Diggs (IRC: joanie) 2018-02-10 16:20:55 UTC

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