protonscr

Open child windows on the same workspace as parent windows on Window Managers

steamopen Steam clientWindow manager
ValveSoftware/steam-for-linux#8218 · opened 2021-11-09 by germaniii · updated 2021-11-10 · 1 comments · github
Ggermaniii 2021-11-09 github

Your system information

  • Steam client version (build number or date): 1634158817 / Built: Oct 13,2021
  • Distribution (e.g. Ubuntu): Arch 5.14.14-1
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

I have tested this on different window managers, qtile, awesomewm, and dwm. Whenever there is an event where a child window is opened, it would open inside the current active workspace instead of the same workspace where the parent window is located.

Steps for reproducing this issue:

  1. I open steam, which usually opens a few windows like the promos and the chat box
  2. When I switch workspaces to open another program, the chat box/promos window would open on the current workspace I am in instead of the same workspace as the main steam client.

Additional Info:

I already submitted an issue on the respective window managers and this is the reply:

This is supported following the X11 spec, so it is up to the programs to provide us with the information to do so. Clients should set the WM_TRANSIENT_FOR hint on child windows to the window ID of their parent window. For example, a xprop on the file open dialog opened by Firefox contains the line WM_TRANSIENT_FOR(WINDOW): window id # 0x3c0002c, which points to the main firefox window and lets us stick it on the correct group (and also positioned centred over the parent

Aarrowgent 2021-11-10 github

hmmmm yes, i have 3 workspaces (workspace switcher) using MATE (gnome2 fork)
though i am usually only active in the first (left most) workspace and have not observed this behavior
i would need to test this effect to repeat the behavior

at first i thought you were talking about monitor area, this also has similar "wrong area" issue
but workspace is different.

im also glad you provided a reasonable additional info

Nothing extracted yet.