GNOME Bugzilla – Bug 648131
Should we (fully) implement or eliminate the desktop abstraction?
Last modified: 2021-07-05 10:45:37 UTC
Currently we have a desktop abstraction, but only one desktop is supported. We should either implement this abstraction fully or eliminate it -- or at least document it properly. :-)
ATK Hackfest conclusions: * No one here really knows what the definition of 'desktop' is in this particular context. * Before we can make an appropriate decision about what to do here we need to first understand what a 'desktop' is, why this implementation was done in the first place, and why currently only one desktop is supported. * There are no problems (other than vast confusion) as a result of this implementation. * Ergo, we will come back to this after higher priority issues have been fully dealt with.
Here is the definition of ATKDesktop in at-spi: typedef struct { AtkObject parent; GdkScreen *screen; } SpiAtkDesktop; So seems ATKDesktop is created for GdkScreen. And from documentation of GdkScreen [1]: This is a currently just a placeholder typedef for the first argument of the window_at_pointer function in GdkPointerHooks. It will be used when GDK gets multihead support. [1] http://developer.gnome.org/gdk/unstable/GdkScreen.html#GdkScreen-struct
See also http://bugzilla.gnome.org/show_bug.cgi?id=108331 (the original bug to implement this)
[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!]
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.