Can you outlne what this means.

The AT-SPI implementation for multiple workspaces (i.e. "desktops" in
at-spi's internal nomenclature) is currently unimplemented, there is
one and only one "desktop" object and all applications are its
"children".  What is needed instead are multiple such
DesktopAccessible objects, one per workspace, and applications should
be children of the appropriate workspace.  These "desktop" objects
then should report state information , etc. and also the root
accessible should see child-changed events when workspaces are added
and removed, etc.

There's some question about how to deal with applications which map
windows onto multiple workspaces; my suggestion would be to make an
exception to the general rule that accessible objects only appear once
in the hierarchy, and map applications onto all workspaces into which
they map toplevel windows.

Secondly we need to ask about applications which map _no_ toplevel
windows; I propose that we treat them the same way as applications
which map to _all_ workspaces, if that is feasible.

I think that implementing this support will require the use of libwnck
API.

Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME
bug list :)

lowering priority until we either identify a more urgent need, or figure out how
we want this to work w.r.t. the above mapping/parent-child issues.

Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.

Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.

[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!]

I'm going to go ahead and close this because it concerns a very old version. Feel free to open a new bug if the problem persists.