Window focus/z-order issue: Maximized Chromium opens behind gnome-text-editor, while non-maximized opens in front

[ffs-akl]

When using shojiwm, the initial z-order/focus behavior of a newly launched window depends on whether the target application opens in fullscreen/maximized mode or windowed mode.
Observed Behavior:
1.Maximized/Fullscreen: The chromium window opens behind gnome-text-editor.

2. Non-maximized (Windowed): The chromium window opens in front of gnome-text-editor.

https://github.com/user-attachments/assets/9a30d6ef-a66c-47ea-805b-055d0ce4bb19
https://github.com/user-attachments/assets/c4c9a011-86d5-4201-a938-077cb6461615

Environment:
OS: Arch Linux
Window Manager: shojiwm-git-0.0.1.alpha.r222.g14b10cd

Applications involved: gnome-text-editor 50.1, chromium 151.0.7922.108

[bea4dev]

@ffs-akl
It doesn’t seem to be reproducible with the default configuration.
Could you share your configuration?

[ffs-akl]

In window-manager.ts, I only changed the padding in the following code to 0:

export const MAXIMIZED_WINDOW_PADDING = {
  top: 0,
  right: 0,
  bottom: 0,
  left: 0,
};

This is my index.tsx:

index.tsx.txt

[bea4dev]

fixed in c2a71b4

[bea4dev]

@ffs-akl
please migrate window-manager.ts

[ffs-akl]

Hi @bea4dev, thanks for the update!
after testing with the latest fix, I found that the issue is still present.
Observed Behavior:
When launching an application in a maximized state, the window initially minimizes/hides into the taskbar instead of appearing on the screen directly. I have to manually click its icon on the taskbar to raise and focus it.
Could you please take another look at how maximized startup windows are handled? Let me know if you need any logs or further testing from my side.

R-2026-08-15T14-06-14.mp4

eidted:
I have migrated window-manager.ts and only changed the padding in the following code to 0:

export const MAXIMIZED_WINDOW_PADDING = {
  top: 0,
  right: 0,
  bottom: 0,
  left: 0,
};

This is my index.tsx:

index.tsx.txt