[Bug] Window open in current workspace, not where is was opened.

[SebasF1349]

Describe the bug

Some apps take a one or two seconds to open (discord as a common example, as it is looking for updates). If I open discord in the second workspace and then I move to the first workspace while it loads, discord ends up opening on the first workspace, which is a bit annoying. It should open on the second workspace instead, as that's where I opened it.

Reproduction

1. Open Discord.
2. Move to another workspace while discord is in the loading screen.

Stack trace or error logs (if applicable)

No response

Version number

3.4.0

[pienapin]

In my experience using various tiling window managers in Linux, like bspwm, awesomewm, and hyprland, I’ve noticed that Discord behaves similarly. It seems that the "looking for updates" and the actual Discord application are different processes. The actual Discord opens only after the "looking for updates" process completes. So, if you switch to the first workspace while the "looking for updates" process is still running, the actual Discord may not have opened yet; that’s why it appears in the first workspace.

As for other apps, they probably haven't fully loaded when you switch to another workspace, resulting in them opening in the new workspace instead. So, in my opinion, this is not a bug; it’s just a common behavior of tiling window managers.

[SebasF1349]

I have not that much experience with tiling wm, I have only used a bit of i3 and now I run hyprland. But hyprland tracks the initial workspace where an app was launched. This is the commit were it was implemented: hyprwm/Hyprland@29308b9 I don't really remember what happened in i3.

But you are probably right. Maybe this is not a bug but a feature request. Will change the label when in my PC.