9a273e1db2
Launching applications on a particular workspace works through launch contexts and startup notifications. While this is no longer required by a launcher/WM split, in theory this allows us to reliably identify the correct window to apply startup properties to. However in practice we fail more often than not: Missing support in toolkits, differences between display protocols, D-Bus activation and single-instance applications all provide their own pitfalls. So instead, take advantage of the fact that launcher and WM live in the same process, and go with the unsophisticated approach: Just remember the last workspace that was requested when launching an app, then move the next window that is associated with the app to that workspace. This will break X11 applications that set an initial workspace, but that's legacy functionality anyway (given that there's no wayland protocol for that functionality), and seems a price worth paying for making launching apps on workspaces more reliable. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1316>
GNOME Shell
GNOME Shell provides core user interface functions for the GNOME 3 desktop, like switching to windows and launching applications. GNOME Shell takes advantage of the capabilities of modern graphics hardware and introduces innovative user interface concepts to provide a visually attractive and easy to use experience.
For more information about GNOME Shell, including instructions on how to build GNOME Shell from source and how to get involved with the project, see the project wiki.
Bugs should be reported to the GNOME bug tracking system.
Contributing
To contribute, open merge requests at https://gitlab.gnome.org/GNOME/gnome-shell.
Commit messages should follow the GNOME commit message guidelines. We require an URL to either an issue or a merge request in each commit.
License
GNOME Shell is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for details.