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 685827 - Current Gtk accessibility support doesn't allow extension
Current Gtk accessibility support doesn't allow extension
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Accessibility
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 686005 (view as bug list)
Depends on:
Blocks: 685828
 
 
Reported: 2012-10-09 17:48 UTC by Alejandro Piñeiro Iglesias (IRC: infapi00)
Modified: 2012-12-27 18:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to move a11y fields in remaining headers to private structures. (112.79 KB, patch)
2012-10-14 17:51 UTC, Mike Gorse
none Details | Review

Description Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-10-09 17:48:09 UTC
Initially discussed on this thread:
https://mail.gnome.org/archives/gtk-devel-list/2012-August/msg00001.html

On Boston summit we resumed this discussion:
http://blogs.gnome.org/mclasen/2012/10/08/gnome-summit-sunday/

Current plan is making public some of the gtk atk implementation API for 3.8. As I said during the summit and [1], I don't think that we need to expose all the APIs, as more of the methods are implementation details. Third party apps will basically need to redefine some ATK methods, so probably just exposing the type of the accessibility classes are enough. As mentioned on the summit, some cleaning (like creating private structures) would be required.

Creating this bug in order to track this problem and to block some of the bugs of those "third-party" apps, like Evince.


[1] https://mail.gnome.org/archives/gtk-devel-list/2012-August/msg00052.html
Comment 1 Matthias Clasen 2012-10-10 02:53:04 UTC
To repeat what was said at the summit: The required tasks here are to:

- review and clean up the a11y headers

- move all members to privates

- write at least some documentation
Comment 2 Mike Gorse 2012-10-11 18:07:04 UTC
I'm working on moving members to privates right now, fyi.
Comment 3 Mike Gorse 2012-10-14 17:51:58 UTC
Created attachment 226418 [details] [review]
Patch to move a11y fields in remaining headers to private structures.
Comment 4 Matthias Clasen 2012-10-15 19:38:24 UTC
mostly done already, I fear.
Comment 5 Matthias Clasen 2012-10-15 20:27:53 UTC
*** Bug 686005 has been marked as a duplicate of this bug. ***
Comment 6 Paul Childs 2012-10-18 01:49:33 UTC
Is it possible for minor patches for current versions to be released (e.g. re: accessing _focus_widget in gail.c and the gtk_widget_class_set_accessible_type errors for custom widgets). 3.8 seems a long time to wait to be able to get accessibility working again. E.g. Debian Wheezy is soon to be released as the new stable for the next two years and is set to use gtk3.4 (similarly Ubuntu 12.04). This will mean that for a long period there will be a lot of people with limited accessibility use under gtk+3.
Comment 7 Emmanuele Bassi (:ebassi) 2012-10-18 07:45:00 UTC
the rule is: no new API is added during a stable cycle, and old stable releases are not updated, except for security issues.
Comment 8 Matthias Clasen 2012-12-27 18:36:58 UTC
I've pushed this now, you need to include gtk-a11y.h