On Wayland-based systems, the native window decorations (minimize, maximize, close) become unresponsive when the window is shown after being initialized as hidden.
Huge thanks to @marsender for reporting this and testing the workarounds!
Confirmed Workaround:
Launching the app with the X11 backend fixes the issue and restores correct button placement:
This appears to be an upstream issue in tao/wry related to how GTK handles Client Side Decorations (CSD) on Wayland when the initial window state is hidden.
On Wayland-based systems, the native window decorations (minimize, maximize, close) become unresponsive when the window is shown after being initialized as hidden.
Huge thanks to @marsender for reporting this and testing the workarounds!
Confirmed Workaround:
Launching the app with the X11 backend fixes the issue and restores correct button placement:
This appears to be an upstream issue in tao/wry related to how GTK handles Client Side Decorations (CSD) on Wayland when the initial window state is hidden.