GNOME Bugzilla – Bug 640949
Review the event API and data sent with events
Last modified: 2021-07-05 10:45:08 UTC
It may be useful for an AT to be able to specify data that it will need when listening for events, so that applications can send some of this data up-front and reduce the need to call back to fetch data. registerEventListener could take a list of properties that it requests from the application, and events could be sent with a dictionary of such properties. Pyatspi currently exposes source_role, source_name, and host_application properties for events. Why are these properties there? If they are intended to facilitate caching, then AT-SPI should be sending them with the event, although, in the current AT-SPI design, name and role should be cached anyhow. host_application currently always points to the object returned by atk_get_root(), so we are sending this object over the wire for an event when it is not used.
Hackfest discussion: * Piñeiro suggests we take advantage of the fact that property-changed events already (in theory) give us the old and new values. * Joanie will make a list of events for which data is "missing". * Suitable new properties will need to be defined (e.g. 'caret-position') * Some debate may still be needed regarding what the old and the new values should be (e.g. in the case of a text-selection change, should the values be the selected strings or the offsets?) * All of the above depends on first sorting out the issues listed in bug 644747.
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports. IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Is this ticket about at-spi2-core or about at-spi2-atk? Asking as this is currently under "api" which will get removed.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/ Thank you for your understanding and your help.