[Bug] Maximizing windows snaps them to previous zones despite "Restore windows to their previous zone" setting being toggled off

[OuToU1]

Description

I have a three zone stacked layout which I use only on my secondary monitor.

When I have a window snapped to one of the zones and move it to my primary monitor, minimizing and then maximizing it moves it to the previously snapped zone which as you can imagine can get very annoying when trying to go between a browser and text editor by minimizing one of them to reveal the other as I often do, just as an example.

This wasn't the case before I recently updated to 3.1.1 (and to 3.1.2 shortly after that) and instead the window stayed where I had placed it. Window floating or maximized, doesn't matter.

"Restore unsnapped windows to their previous position" setting also has no effect on the behavior.

I cannot remember the previous properly working version I was using sadly, I can remember the entire settings page looking very different though if that's anything to go off of.

plasmazones-report-20260701-173333.tar.gz

Expected Behavior

Window stays on primary monitor maximized or where-ever I had it placed floating

Steps to Reproduce

1. Open a new window
2. Snap the window to a zone on secondary monitor
3. Move the window to primary monitor, leave it floating or maximized
4. Minimize and maximize the window
5. The window gets moved to zone on secondary monitor which it was previously snapped in

PlasmaZones Version

3.1.2

Display Server

Wayland

Desktop Environment

Plasma 6.7.1

Distribution

CachyOS

Support Report

No response

Checklist

• I searched existing discussions and issues
• I can reproduce this with default settings

[fuddlesworth]

I was able to reproduce. Looking into it. Fix will roll up with 3.2 as that's close to being released and contains many more bug fixes.

[OuToU1]

Thank you! :)

[OuToU1]

Working as it should in 3.2.0, thank you a ton!

[fuddlesworth]

awesome! sorry for the wait!

[OuToU1]

Hey, the behavior is back with 3.3.2, exact same as described before :/ Unsure about the versions in between. To add, the window first opens on the main monitor for just a tiny bit of time before moving to the previously snapped zone, I cannot remember if this was also happening before or not.

I also noticed that on 3.2.0 it started happening but only on the first remaximize if that makes sense. I would snap a window onto a zone on my secondary monitor, float it to my main monitor and minimizing and maximizing it would send it to the previously snapped zone, but only one time, if I floated it to my main monitor a second time, everything would work as intended.

Not sure why I didn't catch the behavior when I initially reported it working on July 17, my bad.

plasmazones-report-20260731-180655.tar.gz

[fuddlesworth]

nooooo. okay i'll take a look

[OuToU1]

Thanks boss

[OuToU1]

From Discord #general:

"OuToU — 18:35
a new discovery regarding the issue, if i disable the rule which disables snapping on my primary monitor (or in simpler terms if i enable snapping) then remaximizing the window no longer moves it to my secondary monitor

fuddles | PlasmaZones — 18:36
yeah that makes sense since then it's no longer tracking that monitor

OuToU — 18:38
only problem with that really is that if i rightclick to show the zones, even without moving the window to my secondary monitor, the zones get highlighted on my secondary monitor and the window gets snapped as if the zones were on my primary
like the window gets snapped on my primary even without any zones actually existing on it, hopefully you get my explanation :D"

[OuToU1]

2026-07-31.18-45-06.mp4

[fuddlesworth]

Should all be fixed properly in v3.3.3.