GNOME Bugzilla – Bug 649471
Study if AtkSocket/AtkPlug should be interfaces
Last modified: 2021-06-10 11:27:54 UTC
Right now AtkSocket and AtkPlug are direct AtkObject subclasses.
But it would be good to debate if it has more sense to have them as interfaces.
A practical example:
These days, Mario was creating a basic C example for atksocket/atkplug (souce here ).
He needed to redefine the factory for a custom Gtk widget, in order to provide the implementations of AtkSocket/AtkPlug to the accessible hierarchy.
But, as AtkSocket/AtkPlug are AtkObject subclasses, this new object can't be a GtkAccessible subclass. That means that most of the accessible hierarchy would be GtkAccessible subclases, but in the "bridge" part, it wouldn't.
This is not a really big issue, as it is working fine, but means that some of the common things implemented on GtkAccessible (base object management) would be required to be re-implemented on this custom accessible object.
This also applies to AtkGObjectAccessible (ie: used at clutter).
[Mass-reassigning open atk bug reports for better trackability as requested in https://bugzilla.gnome.org/show_bug.cgi?id=653179 .
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 firstname.lastname@example.org 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
and create a ticket at
Thank you for your understanding and your help.