summaryrefslogtreecommitdiff
path: root/Accessibility
diff options
context:
space:
mode:
authorsthibaul <sthibaul@web>2016-02-08 02:24:48 +0100
committerwww <iki-www@freedesktop.org>2016-02-08 02:24:48 +0100
commitc18e33b1ef490a285691493fc20995606e29e50a (patch)
treebcb57670bd70d4b61bf9a2d26a644583166c688d /Accessibility
parentc60f7d4a213d0d064a03b2efcab878c401a7d920 (diff)
Diffstat (limited to 'Accessibility')
-rw-r--r--Accessibility/Walkthrough.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/Accessibility/Walkthrough.mdwn b/Accessibility/Walkthrough.mdwn
index f24769c9..5699facf 100644
--- a/Accessibility/Walkthrough.mdwn
+++ b/Accessibility/Walkthrough.mdwn
@@ -27,6 +27,10 @@ In the case of a Java application:
* `atk_text_get_text` returns it
* `impl_GetText` stuffes the string into a dbus response
+In the case of mozilla:
+* `impl_GetText` and `atk_text_get_text` get called like for a GTK application, the `get_text` method is `getTextCB`
+* `getTextCB` (implemented in `mozilla/accessible/atk/nsMaiInterfaceText.cpp`) uses the `TextSubstring` of the `HyperTextAccessible` class.
+
In the case of a Qt4 application:
* `AtSpiAdaptor::textInterface` (implemented in `qt-at-spi/src/atspiadaptor.cpp`) gets called by qt dbus, it parses the parameters, and calls the `text` method of the `textInterface` of the `QAccessibleInterface` class.
* `QAccessibleTextWidget::text` (implemented in `qt4-x11/src/plugins/accessible/widgets/qaccessiblewidgets.cpp`) fetches the text and returns it.
@@ -35,6 +39,7 @@ In the case of a Qt4 application:
In the case of a Qt5 application:
* `AtSpiAdaptor::textInterface` (implemented in qtbase/src/platformsupport/linuxaccessibility/atspiadaptor.cpp`) gets called by qt dbus, the rest is happening as with Qt4.
+
dbus transmits the response to the application.
* `atspi_text_get_text` gets the string from the response and returns it