Onboard uses the system's at-spi2 framework to get information about newly focused text inputs. However, this requires the applications to also make use of the at-spi2 framework so that Onboard gets informed about their events, like the focussing of a new text input.
Onboard cannot do much about it, if applications don't use the at-spi2 framework. You should rather file bugs against the applications not supporting the at-spi2 framework.
In GTK3 applications, at-spi2 support is included by default, if I remember correctly. And here are the libraries we know of for other applications:
libgail-common
libatk-adaptor # for mozilla applications (XUL based) and ?gtk?
qt-at-spi
libreoffice-gtk
libreoffice-gtk3
libatk-wrapper-java
Onboard uses the system's at-spi2 framework to get information about newly focused text inputs. However, this requires the applications to also make use of the at-spi2 framework so that Onboard gets informed about their events, like the focussing of a new text input.
Onboard cannot do much about it, if applications don't use the at-spi2 framework. You should rather file bugs against the applications not supporting the at-spi2 framework.
In GTK3 applications, at-spi2 support is included by default, if I remember correctly. And here are the libraries we know of for other applications:
libgail-common
libatk-adaptor # for mozilla applications (XUL based) and ?gtk?
qt-at-spi
libreoffice-gtk
libreoffice-gtk3
libatk-wrapper-java