[frameworks-kconfig] [Bug 524481] New: WindowStateSaver force-shows a visible:false window when restoring maximized state

https://bugs.kde.org/show_bug.cgi?id=524481

            Bug ID: 524481
           Summary: WindowStateSaver force-shows a visible:false window
                    when restoring maximized state
    Classification: Frameworks and Libraries
           Product: frameworks-kconfig
      Version First 6.29.0
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

I found a problem with WindowStateSaver in KConfig 6.29.0.

If a QML ApplicationWindow is created with visible: false, it can still become
visible when WindowStateSaver restores a saved maximized state.

I tested this with a minimal QML program and an isolated XDG_STATE_HOME.

When the saved state contains:

Window-Maximized=true

the hidden window becomes visible and maximized. I reproduced this 5/5 times.

The log shows:

VISIBLE_CHANGED visible=true visibility=0
VISIBILITY_CHANGED visible=true visibility=4
COMPLETED visible=true visibility=4

For control, I copied exactly the same saved state and only changed:

Window-Maximized=true

to:

Window-Maximized=false

With that change, the same QML window stayed hidden:

COMPLETED visible=false visibility=0

So the behavior seems specifically connected to restoring the maximized state.

Expected behavior:
If the application creates the window with visible: false, WindowStateSaver
should not make it visible.

Environment:
Arch Linux
KConfig 6.29.0-1
Qt 6.11.1
Plasma 6.7.4
KWin 6.7.4-5
Wayland
Kernel 7.1.8-arch1-3

This looks related to Bug 522205 and the WindowStateSaver change that was
reverted for Frameworks 6.29. I have not tested 6.28, so I cannot confirm the
exact regression range.

-- 
You are receiving this mail because:
You are watching all bug changes.