GNOME Bugzilla – Bug 651358
Document that table {active-descendant, selection}-changed events should include the table row in event.any_data
Last modified: 2021-06-10 11:26:49 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.
[Mass-reassigning open atk bug reports for better trackability as requested in https://bugzilla.gnome.org/show_bug.cgi?id=653179 . PLEASE NOTE: 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 https://bugzilla.gnome.org/userprefs.cgi?tab=email 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.]
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 of atk, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a ticket at https://gitlab.gnome.org/GNOME/atk/-/issues/ Thank you for your understanding and your help.