Re: [g-a-devel] GtkSocket/GtkPlug accessibility
- From: Samuel Thibault <samuel thibault ens-lyon org>
- To: Colomban Wendling <cwendling hypra fr>, Mario Sanchez Prada <msanchez gnome org>, mgorse suse com, Alejandro Piñeiro <apinheiro igalia com>, gnome-accessibility-devel gnome org, gnome-accessibility-list <gnome-accessibility-list gnome org>
- Subject: Re: [g-a-devel] GtkSocket/GtkPlug accessibility
- Date: Tue, 5 Nov 2019 01:23:33 +0100
Samuel Thibault, le jeu. 22 août 2019 18:06:52 +0200, a ecrit:
Samuel Thibault, le jeu. 22 août 2019 13:16:44 +0200, a ecrit:
Now, thinking more about this, maybe there is a way to make all of this
transparent to applications using GtkSocket/GtkPlug:
- introduce the at-spi objects I mentioned in my Aug 14th mail
- make GtkPlug expose the at-spi path as a _NET_WM property.
- make gtk_socket_add_window try to read it, and if it exists, call
atk_socket_embed on it
That should be working both for the mate-panel implementation mentioned
above, and for tray icons. And for anything that uses GtkPlug/Socket.
Here is what is looks like, it looks quite fine in the end, what do
people think?
Arguably, the AtkPlugExt part could be stuffed into AtkPlug:
That part got committed to atk. I eventually submitted it to:
https://gitlab.gnome.org/GNOME/gtk/merge_requests/1147
Samuel
[Date Prev][Date Next] [Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]