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 758298 - Entry completion pop-up items initially fail to emit object:state-changed:selected accessibility events
Entry completion pop-up items initially fail to emit object:state-changed:sel...
Status: RESOLVED DUPLICATE of bug 711397
Product: gtk+
Classification: Platform
Component: Accessibility
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-11-18 16:50 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-02-10 15:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
pyatspi accessible-event listener (212 bytes, text/x-python)
2015-11-18 16:50 UTC, Joanmarie Diggs (IRC: joanie)
Details

Description Joanmarie Diggs (IRC: joanie) 2015-11-18 16:50:07 UTC
Created attachment 315844 [details]
pyatspi accessible-event listener

Steps to reproduce:
1. Launch the attached accessible-event listener in a terminal
2. Quit the Entry Completion demo if it's open
3. Launch gtk3-demo's Entry Completion demo
4. Type "t" to cause the completion pop up to appear
5. Down arrow twice

Expected results: object:state-changed:selected (true) events emitted as the selection changes

Actual results: no object:state-changed:selected (true) events emitted as the selection changes -- initially.

Note: If, after completing step 5, you up arrow, the events are emitted. If you then re-down arrow, they are emitted. And they'll continue to be emitted as expected even after the entry completion is collapsed (hence step 2 above).

Impact: Because the events are initially missing, Orca doesn't present the selection changes.
Comment 1 Matthias Clasen 2018-02-10 05:09:21 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 15:29:28 UTC

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