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 638537 - Metabug: bugmap towards ATK 3.0
Metabug: bugmap towards ATK 3.0
Product: atk
Classification: Platform
Component: atk
Other Linux
: Normal normal
: ---
Assigned To: ATK maintainer(s)
ATK maintainer(s)
Depends on: 326538 345750 363439 407539 551489 551680 598952 611507 638377 638378 638924 639466 639470 639479 639486 640440 640625 640949 642597 644393 644508 644747 647351 647352 647357 647482 647486 647488 648131 648259 648260 648616 648675 649123 649471 649556 649559 649575 649577 649771 649804 649805 649879 649902 651343 651345 651349 651353 651358 651367 651368 651369 651370 651407 652548 652777 653244 653246 653291 653292 653293 653874 665598 665599 666918 668119 668439 672368 696302
Reported: 2011-01-02 21:37 UTC by Alejandro Piñeiro Iglesias (IRC: infapi00)
Modified: 2021-06-10 11:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Alejandro Piñeiro Iglesias (IRC: infapi00) 2011-01-02 21:37:52 UTC

During the definition of the GNOME Accessibility Team Roadmap, it was included a point related to ATK [1]. ATK has worked for more than 10 years, and worked pretty well during that time, but the experience during those years showed that it can be improved. The items defined on that roadmap are a example of that.

During one of the accessibility meetings [2] it was discussed one of the changes required and compared with Gtk3 upcoming release, that include several API/ABI breakage. Several of the issues detected were most than new additions, and would require API changes/break so the concept of a new ATK 2.0 started to makes sense.

During the same meeting it was also suggested to create a ATK/AT-SPI hackfest during April, idea that was later discussed on following meetings [3][4].


The purpose of this bug is serves as a metabug of this ATK revamp. Some of the bugs included would be also applied as ATK 1.0 add-ons, but it is mostly intended to organize and discuss changes that would require a new ATK 2.0

This would be start as a metabug that includes all the tasks defined on the roadmap [1], but then it would be improve with additional suggestions towards ATK 2.0

Comment 1 Fernando Herrera 2011-03-11 17:51:57 UTC
just a quick pointer to IA2 proposed changes for 1.3:
Comment 2 Alejandro Piñeiro Iglesias (IRC: infapi00) 2011-06-13 14:45:54 UTC
Well, as Li Yuan commented on the hackfest, last ATK release has a 2.0.0 version number. Anyway, don't remember what it was needed (Li?)

Anyway, that means that this metabug manages the work towards ATK 3.0. So updating the summary accordingly ...
Comment 3 André Klapper 2011-06-23 22:05:23 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 4 André Klapper 2021-06-10 11:26:44 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.