GNOME Bugzilla – Bug 663732
Newly-added widgets do not initially emit events until an AT "drills down" the accessible hierarchy
Last modified: 2021-07-05 10:48:47 UTC
Created attachment 201098 [details] test case: progressbar.py Steps to reproduce: 1. Run the attached test case (progressbar.py) 2. Run the attached test script (test_pbar.py) 3. In the Progress! GtkWindow, press the button to add a progress bar 4. Wait a while and then press F11 (or just sit there) 5. Press F12 to terminate the test script (test_pbar.py) Note: After step 3, each time the GtkProgressBar updates its value, the update count is printed in the terminal from which you launched the test case. Note: After step 4, each time an accessible property-change event is emitted, the event count is printed in the terminal from which you launched the test script. Expected results: The update count and the event count would match. Actual results: The update count begins and continues as expected. But no accessible events are being seen. After you press F11 to "drill down" the accessible hierarchy, the accessible events start showing up -- most of the time. On occasion, even the drill down is insufficient to cause the expected events to occur.
Created attachment 201099 [details] test script/listener: test_pbar.py
I think the atk object for the new widget is being lazily created as a side effect of emitting the children-changed event, and a children-changed event isn't being emitted because gtk_grid_attach doesn't generate an "add" signal that gtkcontaineraccessible.c relies on to generate the event (essentially the same issue as bug 577392).
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports. IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
Reviewing bugzilla due our conversation about Caribou at the GUADEC 2013 a11y bof. I think that this is obsolete, due the "accessibility always on" change, and that we could close it. Joanmarie could you confirm that?
This bug still exists and can be reproduced exactly as described in the opening report. I am using F19 (GNOME 3.8) FWIW.
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Is this ticket about at-spi2-core or about at-spi2-atk? Asking as this is currently under "general" which will get removed.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/at-spi2-atk/-/issues/ Thank you for your understanding and your help.