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 748311 - Missing accessible object:state-changed:focused events for terminal widgets
Missing accessible object:state-changed:focused events for terminal widgets
Status: RESOLVED DUPLICATE of bug 711397
Product: gtk+
Classification: Platform
Component: Accessibility
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 747486 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-04-22 16:09 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-02-10 15:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
accessible-event listener (988 bytes, text/x-python)
2015-04-22 16:09 UTC, Joanmarie Diggs (IRC: joanie)
Details

Description Joanmarie Diggs (IRC: joanie) 2015-04-22 16:09:52 UTC
Created attachment 302164 [details]
accessible-event listener

Steps to reproduce:
1. Launch the attached accessible-event listener in xterm or vte. [*]
2. Launch gnome-terminal.
3. Press Return a couple of times to cause text to be inserted.
4. Press Ctrl+Shift+T to create a new tab.
5. Repeat step 3 for the newly-created tab.

Expected results:
1. After step 4, an object:state-changed:focused event would be emitted for the terminal in the new tab.
2. After step 5, the text-changed events would say the source is focused, just like occurred after step 3.

Actual results:
1. After step 4, the terminal which gave up focus does emit a state-changed event to indicate it gave up focus (this is good). But the new terminal does not emit this event claiming focus.
2. After step 5, the text-changed events say the source is not focused.

Impact: Orca deliberately ignores text-changed events in non-focused terminals because it's quite common for a non-focused terminal to be emitting text-changed events (package manager output, compiling output, etc.). But as a result of that, Orca is not presenting text in certain focused terminals because Orca doesn't know the terminals are focused.

[*] Note: The listener prints out text-changed events from gnome-terminal. You do not want to log the events resulting from logging the events. ;)
Comment 1 Joanmarie Diggs (IRC: joanie) 2015-04-22 16:10:44 UTC
*** Bug 747486 has been marked as a duplicate of this bug. ***
Comment 2 Christian Persch 2015-04-22 18:45:02 UTC
Hmm. VteTerminal doesn't do anything special here, changing the a11y focus state is done in GtkWidgetAccessible which VteTerminalAccessible derives from. Does this happen with other apps with notebooks (gedit, or just about any prefs dialogue)? There is a gtk bug somewhere with missing focus events (bug 677329) so this might be just another manifestation of that.
Comment 3 Joanmarie Diggs (IRC: joanie) 2015-04-22 19:34:48 UTC
Aha. It's yet another (yet another, yet another...) case where Gtk+ is giving us focus: events (deprecated) and failing to give us object:state-changed:focused events. <insert sigh here>

Will transfer to Gtk+. In the meantime, I added yet another hack to Orca for this.

Thanks Christian for the quick triage!
Comment 4 Matthias Clasen 2018-02-10 05:25:19 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 5 Joanmarie Diggs (IRC: joanie) 2018-02-10 15:12:40 UTC
Rather than re-open this bug, making it a dup of bug 711397 which I've just turned into a generic "missing initial object:state-changed:focused events" bug.

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