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 654405 - Focused tables initially lack ATK_STATE_FOCUSED
Focused tables initially lack ATK_STATE_FOCUSED
Status: RESOLVED DUPLICATE of bug 711397
Product: gtk+
Classification: Platform
Component: Accessibility
3.1.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-07-11 15:55 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-02-10 16:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test script (388 bytes, text/x-python)
2011-07-11 15:56 UTC, Joanmarie Diggs (IRC: joanie) 		Details

Description Joanmarie Diggs (IRC: joanie) 2011-07-11 15:55:09 UTC 
Steps to reproduce (order counts):

1. Launch gtk-demo
2. Run the attached event listener in a terminal window
3. Launch the editable cells demo
4. As soon as the window for the demo is opened, arrow around

Expected results: the focused table in which you are arrowing around would claim to be focused.

Actual results: the focused table apparently lacks this state.

5. Alt+Tab once to remove focus from the editable cells demo window.
6. Alt+Tab once more to return focus to the editable cells demo window.
7. Repeat step 4.

This time the focused table claims to be focused.

(Note: This is not new to the gail integration.)
Comment 1 Joanmarie Diggs (IRC: joanie) 2011-07-11 15:56:12 UTC 
Created attachment 191734 [details]
test script
Comment 2 Matthias Clasen 2018-02-10 05:13:51 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 3 Joanmarie Diggs (IRC: joanie) 2018-02-10 16:02:19 UTC 

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