On 08/31/2015 02:40 AM, Alejandro Piñeiro wrote: > > > On 29/08/15 23:31, Samuel Thibault wrote: >> Hello, >> >> I'm working on the AT-SPI2 driver of brltty, and there is something we >> are doing very oddly: finding out which widget is currently active. At >> the moment what we do is starting from the AT-SPI root, and recursively >> look at children until we find one which is focused and has an active >> parent. > > As far as I know something like that is what Orca does (Joanmarie can > confirm).
I think the bug you subsequently pointed to confirms it: > There is an open bug about that: > https://bugzilla.gnome.org/show_bug.cgi?id=651368 As I stated in comment 7 of that bug: Well, that strikes me as being the tree diving that Orca already does -- when Orca is forced to do it. Orca tries to avoid doing it by keeping track of the active widget. --joanie _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
