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 651358 - Document that table {active-descendant, selection}-changed events should include the table row in event.any_data
Document that table {active-descendant, selection}-changed events should incl...
Product: atk
Classification: Platform
Component: atk
git master
Other Linux
: Normal normal
: ---
Assigned To: ATK maintainer(s)
ATK maintainer(s)
Depends on: 639479 651343
Blocks: 638537
Reported: 2011-05-28 23:22 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2021-06-10 11:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Joanmarie Diggs (IRC: joanie) 2011-05-28 23:22:05 UTC
As agreed upon at the ATK hackfest, for tables in which an entire row can be selected, we expect (and typically get) one or both of the following events:

* object:selection-changed
* object:active-descendant-changed

What we currently do NOT get in the event's any_data is the associated row object. This is not surprising since we currently do not have official row objects. ;-) But that shall change. See bug 639479 and bug 651343.

Therefore, the fact that the to-be-created and used ATK_TABLE_ROW should be sent in the aforementioned events' any_data needs to be documented.
Comment 1 André Klapper 2011-06-23 22:05:36 UTC
[Mass-reassigning open atk bug reports for better trackability as requested in .
If you have watched the previous assignee of this bug report as a workaround for actually getting notified of changes in atk bugs, you yourself will now have to add atk-maint@gnome.bugs to your watchlist at the bottom of to keep watching atk bug reports in GNOME Bugzilla.
Sorry for the noise: Feel free to filter for this comment in order to mass-delete the triggered bugmail.]
Comment 2 André Klapper 2021-06-10 11:26:49 UTC
GNOME is going to shut down in favor of
As part of that, we are mass-closing older open tickets in
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 of atk, then please follow
and create a ticket at

Thank you for your understanding and your help.