GNOME Bugzilla – Bug 663726
Newly-added widgets do not initially emit focused events
Last modified: 2021-07-05 10:48:38 UTC
Created attachment 201091 [details] test case: widgets.py Steps to reproduce: 1. Run the attached test case (widgets.py) 2. Run the attached test script (onfocused.py) 3. In the widgets GtkWindow: a. Press the button for the widget you wish to create b. Move focus to the new widget c. Move focus off the new widget d. Move focus back to the new widget 4. Press F12 to terminate the test script (onfocused.py) Expected results: Every time a widget in widgets.py gets focus, an object:state-changed:focused event with detail1 == 1 would be seen. Actual results: The first time any newly-added widget gets focus, there is no associated object:state-changed:focused event for that widget (Step 3b). But the next time you give the newly-added widget focus, there will be the appropriate event as expected (step 3d).
Created attachment 201092 [details] test script/listener: onfocused.py
[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.