summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix use after free when an event listener is destroyedgnome-3-34Mike Gorse2020-06-161-6/+4
| | | | | | Properly remove event listeners from the list when they are deregistered. Fixes a crash that can happen when orca exits. Similar issue to https://gitlab.gnome.org/GNOME/at-spi2-core/issues/22
* Fix use-after-free when a device listener is destroyedColomban Wendling2020-06-111-1/+3
| | | | Fixes #22.
* Fix source reproducibilityJoshua Watt2019-11-201-1/+1
| | | | | | | | | The generated enum type files can be included in source packages meant for debugging, and thus need to be reproducible. Replace the absolute include of the header with the basename. This is sufficient because the target include files are always in the include path anyway. Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
* 2.34.0AT_SPI2_CORE_2_34_0Mike Gorse2019-09-092-1/+7
|
* Update doapMike Gorse2019-09-091-15/+12
|
* Merge branch 'at_spi_bus' into 'master'Mike Gorse2019-09-081-11/+18
|\ | | | | | | | | | | | | At spi bus mutual exclusion fixes Closes #18 See merge request GNOME/at-spi2-core!24
| * at-spi-bus-launcher: defer starting atspi bus after bus name acquiredSamuel Thibault2019-09-061-10/+12
| | | | | | | | | | | | | | In case bus name acquisition fails, we should not have started a bus after all, but worse, we should not have written its address in the AT_SPI_BUS X root property. We should thus do them only after having acquired the bus name.
| * at-spi-bus-launcher: Only clear AT_SPI_BUS X prop when having set itSamuel Thibault2019-09-061-1/+5
| | | | | | | | | | In case where bus name acquisition fails, we shall not drop the AT_SPI_BUS X property of the existing daemon.
| * at-spi-bus-launcher: clear a11y_bus_pid when failing to read addressSamuel Thibault2019-09-061-0/+1
| | | | | | | | | | | | This may happen if dbus-daemon spawns but fails to start. In that case after terminating it we should forget its pid, to avoid trying to terminate it again at the end of main().
* | Fix use after free when freeing an eventMike Gorse2019-09-041-1/+1
|/
* 2.33.92AT_SPI2_CORE_2_33_92Mike Gorse2019-09-022-1/+11
|
* Up meson requirementMike Gorse2019-09-021-1/+1
|
* Merge branch 'wip/lantw/meson-only-link-to-libdl-when-it-is-necessary' into ↵Mike Gorse2019-09-021-1/+7
|\ | | | | | | | | | | | | 'master' meson: Only link to libdl when it is necessary See merge request GNOME/at-spi2-core!23
| * meson: Only link to libdl when it is necessaryTing-Wei Lan2019-09-021-1/+7
|/ | | | | | | | | | | Recent FreeBSD releases add libdl to the system, which just includes a few stub functions already included in libc. Since it only exists for GNU/Linux compatibility and does nothing useful, it may be better to avoid linking to it when dlopen can be found in libc. This commit modifies the libdl check to mimic the code in the removed configure.ac file, so libdl is only used when dlopen can't be found without using -ldl.
* Update INSTALLMike Gorse2019-08-281-14/+14
| | | | Fixes https://gitlab.gnome.org/GNOME/at-spi2-core/issues/1
* Clarify atspi_editable_text_insert_text documentationMike Gorse2019-08-281-2/+2
| | | | | | | Clarify that the length parameter expects a count of bytes. This matches the corresponding atk documentation. Fixes https://gitlab.gnome.org/GNOME/at-spi2-core/issues/9
* Relicense as LGPL 2.1Mike Gorse2019-08-2883-424/+444
| | | | Fixes https://gitlab.gnome.org/GNOME/at-spi2-core/issues/2
* Fix outdated FSF addressMike Gorse2019-08-2781-163/+163
|
* Merge branch 'early_quit_warn' into 'master'Mike Gorse2019-08-261-2/+3
|\ | | | | | | | | misc: Do not warn on no reply from pending get_items call See merge request GNOME/at-spi2-core!22
| * misc: Do not warn on no reply from pending get_items callSamuel Thibault2019-08-251-2/+3
| | | | | | | | | | | | | | | | Like DBUS_ERROR_SERVICE_UNKNOWN, this may happen in normal use. For instance, during the at-spi2-atk testsuite, in the atk_test_accessible_set_cache_mask testcase, we may make the application quit before get_items gets to be replied to.
* | Merge branch 'warn' into 'master'Mike Gorse2019-08-262-2/+10
|\ \ | |/ |/| | | | | Fix warnings while running the "memory" test See merge request GNOME/at-spi2-core!21
| * cleanup: Avoid disposing NULLSamuel Thibault2019-08-251-1/+2
| | | | | | | | | | | | In case atspi_application_dispose was previously called for an application, the app field of its root will be NULL. In such a case cleanup should not try to dispose it.
| * atspi_accessible_dispose: Avoid unreferencing NULLSamuel Thibault2019-08-251-1/+8
|/ | | | | | | | The children array may contain NULL entries, when the children have not all been inspected yet for instance. In such a case atspi_accessible_dispose's call to g_ptr_array_free would warn out when freeing array items with g_object_unref. We should thus check for NULL to avoid such warning.
* 2.33.90AT_SPI2_CORE_2_33_90Mike Gorse2019-08-052-1/+12
|
* Support mutter remote desktop interface for key/mouse eventsMike Gorse2019-08-057-0/+489
| | | | | | | | | | | | | | Mutter now has a remote desktop interface with methods to synthesize keyboard and mouse events. This functionality has not been available through AT-SPI on wayland since it uses X-specific functions. Also add atspi_set_reference_window. Probably a work in progress; doesn't appear to be behaving as intended. Also requires that introspection be enabled on gnome-shell. Ie, gsettings set org.gnome.shell introspect true https://bugzilla.gnome.org/show_bug.cgi?id=709999 https://gitlab.gnome.org/GNOME/at-spi2-core/issues/14
* Merge branch 'get_type' into 'master'Mike Gorse2019-08-011-0/+2
|\ | | | | | | | | Add missing atspi_application_get_type prototype See merge request GNOME/at-spi2-core!20
| * Add missing atspi_application_get_type prototypeSamuel Thibault2019-08-011-0/+2
|/ | | | This is needed to be able to use macros such as ATSPI_APPLICATION().
* Merge branch 'master' into 'master'Mike Gorse2019-07-251-2/+2
|\ | | | | | | | | Fix typos See merge request GNOME/at-spi2-core!19
| * Fix typosSamuel Thibault2019-07-251-2/+2
|/
* Add a sender to the AtspiEvent struct.Mike Gorse2019-07-182-1/+7
| | | | | | | | | | Normally, this is set to the application / root accessible from the application corresponding to the event source, but screen-reader-generated events are actually generated by the screen reader. The sender is set based on the application that sent the signal over dbus, so, in the latter case, this will be set to the screen reader. Per discussion at https://gitlab.gnome.org/GNOME/orca/issues/36
* Refactor the API for the screen reader to notify listeners of its statusMike Gorse2019-07-1811-136/+178
| | | | | | | Remove atspi_text_notify_reading_position, and instead add a region_changed signal. Also make the dbus API more like the API used for other events. Per discussion at https://gitlab.gnome.org/GNOME/orca/issues/36
* 2.33.2AT_SPI2_CORE_2_33_2Mike Gorse2019-06-171-0/+12
|
* Merge branch 'solaris' into 'master'Mike Gorse2019-06-171-0/+1
|\ | | | | | | | | Add /usr/lib/dbus-daemon to list of paths to check in See merge request GNOME/at-spi2-core!17
| * Add /usr/lib/dbus-daemon to list of paths to check inAlan Coopersmith2019-06-161-0/+1
|/ | | | | | This is where Solaris installs it. Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
* Bump versionMike Gorse2019-06-141-1/+1
|
* Merge branch 'ins-and-del' into 'master'Mike Gorse2019-06-151-1/+9
|\ | | | | | | | | Add ATSPI_ROLE_CONTENT_DELETION and ATSPI_ROLE_CONTENT_INSERTION See merge request GNOME/at-spi2-core!16
| * Add ATSPI_ROLE_CONTENT_DELETION and ATSPI_ROLE_CONTENT_INSERTIONJoanmarie Diggs2019-06-131-1/+9
|/ | | | https://gitlab.gnome.org/GNOME/at-spi2-core/issues/4
* Merge branch 'mod5' into 'master'Mike Gorse2019-06-111-0/+13
|\ | | | | | | | | deviceeventcontroller-x11.c: Also try mod4 and mod5 to generate keysyms See merge request GNOME/at-spi2-core!15
| * deviceeventcontroller-x11.c: Also try mod4 and mod5 to generate keysymsSamuel Thibault2019-06-081-0/+13
| | | | | | | | | | Notably azerty's altgr modifier is mapped on mod5, so we need to try it too to get more than half of the non-alphabetic characters.
* | NEWS: fix typoMike Gorse2019-05-211-1/+1
| |
* | Merge branch 'wip/carlosg/wayland-session-checks' into 'master'Mike Gorse2019-05-223-4/+5
|\ \ | |/ |/| | | | | Resort to WAYLAND_DISPLAY checks to avoid X11 connections See merge request GNOME/at-spi2-core!14
| * Resort to WAYLAND_DISPLAY checks to avoid X11 connectionsCarlos Garnacho2019-05-213-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | Same reasoning applies (Opening and closing X11 displays may be from ineffective to harmful there), but the XDG_SESSION_TYPE check breaks for startx. Explicitly check that DISPLAY is present but WAYLAND_DISPLAY is not, in order to avoid this behavior. Pointed out at https://gitlab.gnome.org/GNOME/at-spi2-core/merge_requests/12
* | 2.33.1AT_SPI2_CORE_2_33_1Mike Gorse2019-05-202-1/+13
| |
* | Merge branch 'reading-position-endoffset' into 'master'Mike Gorse2019-05-202-24/+7
|\ \ | |/ |/| | | | | atspi_text_notify_reading_position: let caller specify end offset See merge request GNOME/at-spi2-core!13
| * atspi_text_notify_reading_position: let caller specify end offsetSamuel Thibault2019-05-102-24/+7
| | | | | | | | since the screen reader may not be speaking until the end of the text.
* | Merge branch 'wip/carlosg/x11-session-checks' into 'master'Mike Gorse2019-05-203-75/+30
|\ \ | |/ |/| | | | | Check for X11 session before using X11 paths See merge request GNOME/at-spi2-core!12
| * Only use x11 device event controller implementation on X11 sessionsCarlos Garnacho2019-05-061-1/+1
| | | | | | | | | | | | A wayland compositor would be impervious to the actions performed there, so it only could only partially work with other X11 clients. That doesn't seem like the intended effect.
| * Do not rely on getenv("DISPLAY")!=NULL to assume it is a X11 environmentCarlos Garnacho2019-05-062-27/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Change/add checks around the AT_SPI_BUS root window property handling so it is only done if the session is a real X11 one. These checks used to work on wayland sessions, as there still is a X server to poke, it's strange to use as a side channel but that's about it. However in the future mutter will start Xwayland on demand, the DISPLAY environment variable will definitely exist so checking for it is definitely not sufficient, and opening the display will unintendedly spawn Xwayland. It is debatable that this should happen in Wayland sessions at all, so let the org.a11y.Bus fallbacks take over.
| * bus-launch: Do not poke X11 to check at-spi-bus-launcher is runningCarlos Garnacho2019-05-061-47/+0
|/ | | | | | | | | | | | The already_running() check first gets the AT_SPI_BUS root window property, then tries to open it to check if it exists. For it to exist though there must be another at-spi-bus-launcher process around with the org.a11y.Bus name. It seems we can just defer the uniqueness check to g_bus_own_name(), as we will get the "name lost" callback right after failing to acquire the unique name. Doing it this way works for both x11 and non-x11, and avoids assumptions on what the current windowing actually is.
* More updates related to reading position notificationsMike Gorse2019-05-056-64/+114
| | | | | | | | | Allow a client to receive notifications through AtspiEventListeners. This involves special casing, since the event is generated by the screen reader, not the GUI, and is, thus, handled by a different DBus interface, but, from the client's perspective, it looks like a normal AT-SPI event. Also renamed atspi_text_notify_read_position to atspi_text_notify_reading_position and fixed a few warnings.