| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The definition of the signal declares 0 arguments, so the listener can't
assume there are any.
Found by Michael Stahl via this valgrind snippet:
==4770== Conditional jump or move depends on uninitialised value(s)
==4770== at 0x3104C10812: text_selection_changed_event_listener
(event.c:1036)
==4770== by 0x30EF42160A: signal_emit_unlocked_R (gsignal.c:3519)
==4770== by 0x30EF42A180: g_signal_emit_valist (gsignal.c:3309)
==4770== by 0x30EF42A8F9: g_signal_emit_by_name (gsignal.c:3405)
==4770== by 0x1835EE96:
AtkListener::notifyEvent(com::sun::star::accessibility::AccessibleEventObject
const&) (atklistener.cxx:454)
==4770== by 0x56E46BA:
comphelper::AccessibleEventNotifier::addEvent(unsigned int,
https://bugzilla.gnome.org/show_bug.cgi?id=741734
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=684076
|
|
|
|
|
|
|
|
|
|
| |
As it was implemented, the default attributes are appended to the end
of the list, and later in time only the last occurence of every
attribute will be preserved.
Just changing the order of the list fixes this bug.
https://bugzilla.gnome.org/show_bug.cgi?id=731980
|
|
|
|
|
|
| |
Requires.Private should be Requires.private.
https://bugzilla.gnome.org/show_bug.cgi?id=721719
|
| |
|
|
|
|
|
|
|
| |
Hopefully this will improve performance when, ie, gtk floods us with
children-changed events when populating a large treeview.
https://bugzilla.gnome.org/show_bug.cgi?id=728319
|
|
|
|
|
|
|
|
|
| |
We should try not to leave stale sockets and their directories when exiting.
They are removed when calling atk_bridge_adaptor_cleanup, but gtk does not
currently call this function when exiting, and there is not a good place
to call it from gtk.
https://bugzilla.gnome.org/show_bug.cgi?id=684076
|
| |
|
|
|
|
|
|
|
|
| |
This commit:
9eae1f7c2b818b5bd702f99ed97056ca76ea01f6
Started to use some methods not included until 1.5, so bumping the
version needed
|
| |
|
|
|
|
|
| |
Add_event_from_iter checks for the old form anyway, so might as well
allow it. Improves compatibility with at-spi2-registryd <= 3.10.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Handle requests for additional data from event listeners (ie, registered with
atspi_event_listener_register_full), and allow sending interfaces and screen
extents in this way.
https://bugzilla.gnome.org/show_bug.cgi?id=708695
|
| |
|
|
|
|
|
|
| |
It also bumps the atk dependency
https://bugzilla.gnome.org/show_bug.cgi?id=719508
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=712609
|
|
|
|
| |
New roles are present in 2.11.2 and later.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=712608
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=710464
|
| |
|
|
|
|
|
|
|
| |
The method call should be called Contains, not contains, per the D-Bus and
AT-SPI specs.
https://bugzilla.gnome.org/show_bug.cgi?id=710730
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=700865
|
|
|
|
|
|
|
|
| |
If we time out waiting for a keystroke listener, then exit the main
loop, and reset the DBus connections' main loop contexts becak to the
default loop.
https://bugzilla.gnome.org/show_big.cgi?id=707218
|
| |
|
|
|
|
|
|
| |
Also, raised the version of the ATK dependency up to 2.9.4.
https://bugzilla.gnome.org/show_bug.cgi?id=705581
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a key event was sent out and there was also a listener in the same
process, then the listener would never see the event, since the main
loop was being run in a separate context, while libatspi would defer
handling of the event, adding an idle handler into the default context.
We should call atspi_set_main_context (new function) to let libatspi
know which context to use when adding an idle callback. This was
previously hacked around by setting ATSPI_CLIENT in pyatspi and avoiding
switching main loop contexts if it was set, but this was specific to
pyatspi (ie, did not take into account direct usage of libatspi or use
directly through introspection, such as in Javascript), so this check
was removed in 2.9.3.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, direct D-Bus connections were not exposed if AT_SPI_CLIENT
was set in the environment, since they are causing deadlock if the
application and the AT are in the same process. However, AT_SPI_CLIENT
was only being set by pyatspi, meaning that libatspi consumers not using
pyatspi (Javascript embedded in gnome-shell that uses the libatspi
introspection bindings directly, for instance) would still have problems
when attempting to inspect their own accessibles.
Also removed the code in event.c to disable main loop context switching
when AT_SPI_CLIENT was set. Modifying it to also check
atspi_is_initialized would cause deadlock with gnome-shell when Orca is
running. Hopefully that code is not needed anymore.
|
| |
|
|
|
|
|
|
|
|
| |
If atk_object_ref_accessible_child returns NULL when creating the cache,
then don't attempt to process/unref the NULL item, although applications
probably shouldn't be returning NULL in response to a call to
atk_object_ref_accessible_child, so it seems debatable whether we should
be printing a warning here.
|
|
|
|
|
|
|
|
|
|
| |
Register_reply could access invalid memory if it is called after
atk_bridge_adaptor_cleanup() has been called.
This code should probably be refactored to make the instance act as a
GObject, but committing this for now to fix the crash.
https://bugzilla.gnome.org/show_bug.cgi?id=699554
|
| |
|
|
|
|
|
|
|
| |
Call dbus_error_free in some cases where it is needed. Just pass NULL to
dbus_message_get_args where we aren't using the error.
https://bugzilla.gnome.org/show_bug.cgi?id=698951
|
| |
|