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 654410 - focus-related states and signals for menu items need sorting out
focus-related states and signals for menu items need sorting out
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 17:55 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-02-10 15:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test script (458 bytes, text/x-python)
2011-07-11 17:55 UTC, Joanmarie Diggs (IRC: joanie)
Details

Description Joanmarie Diggs (IRC: joanie) 2011-07-11 17:55:37 UTC
Created attachment 191747 [details]
test script

Steps to reproduce (order counts):

1. Launch gtk-demo
2. Run the attached event listener in a terminal window
3. Launch the Application main window demo
4. Press Alt+F and arrow up/down amongst the menu items

Results:

1. When the menu first opens, there are no AT-SPI events indicating focus has changed. Based on the documentation[1], these events are expected. (And failing that, we need to clarify the ATK docs. But assuming for the moment that it is agreed that menu items should claim focus...)

2. For subsequent arrow presses, a focus: event is seen. But the state set lacks this state. In addition, an object:state-changed:focused event is NOT seen. Note that this happens to be the complete opposite of what the new world order shall be. As stated in bug 651367, focus: is seen as being redundant given object:state-changed:focused, and it's slated for deprecation.

(Note: This is NOT new to the gail integration.)

[1]From http://developer.gnome.org/atk/unstable/atk-AtkState.html:
   ATK_STATE_FOCUSED
   Indicates this object currently has the keyboard focus
Comment 1 Matthias Clasen 2011-07-17 00:39:49 UTC
I have started tests/a11y/testfocus.c to explore the differences between GTK+'s and gails notions of focus.
Comment 2 Hammer Attila 2011-10-28 05:15:35 UTC
I confirm Joanie reported issue.

Attila
Comment 3 Hammer Attila 2012-02-21 14:02:50 UTC
Matthias, your openion have chance fixing this bug before GNOME 3.4 final release?

I using Orca Screen Reader, and very missing the first menu bar item spokening when I activating a menu bar with F10 key.
Now, when I want hearing what the first main menu an application, need doing following key sequences:
1. Press F10 key (activating the menu bar). Orca not speaking the first selected main menu.
2. Press right arrow key. Orca now speaking the second main menu.
3. Press left arrow key. Orca speaks the first main menu.

Attila
Comment 4 Matthias Clasen 2012-02-22 09:07:34 UTC
No, a11y focus handling fixes are not on the radar for 3.4
Comment 5 Matthias Clasen 2012-02-22 11:16:25 UTC
No, a11y focus handling fixes are not on the radar for 3.4
Comment 6 Hammer Attila 2012-03-21 05:30:14 UTC
Hy Joanie,

I have got a good news, I don't no upstream level you experiences is equals good:
In my Ubuntu 12.04 system now upgraded with GTK3 related packages with 3.3.20 version. After all upgrades are installed the main menu items Orca spokening again.
If I press F10 key, Orca right spokening the first focused main menu in any application, prewious this is not happened.

Attila
Comment 7 Matthias Clasen 2018-02-10 05:05:49 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 8 Joanmarie Diggs (IRC: joanie) 2018-02-10 15:48:32 UTC
Making this one yet another dup of bug 711397 based on what's in the opening report, namely: not getting expected events but seeing the deprecated focus: events.

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