Cycling sizes issue when it should not (checks width only not height)

[picklejw]

• This is a new bug that hasn't been documented in a closed issue or in the Readme.

I do not see this bug reported, I have my config set for 'Repeated Commands' with cycle on side actions and cycle quadrants and size on side.

When I position window to lower right repositioning to upper right works correct and not cycle sizes. But if I am on lower right then keyboard to full right side instead of just filling up to top of screen it will do that but also 'cycle' to a different width (then 50% which is what I expect). Guessing some check when resizing that it is not checking previous height with width when resizing so it thinks it needs to cycle different widths.

macOS version: Tahoe 26.6.1
Rectangle version: 0.98
Logs if applicable (In Rectangle menu, hold option, "View Logging..."):
2026-08-19T14:59:52-04:00: AX position proposed: (1504.0, 861.0), result: (1504.0, 861.0)
2026-08-19T14:59:52-04:00: AX sizing proposed: (1504.0, 831.0), result: (1504.0, 831.0)
2026-08-19T14:59:52-04:00: bottomRight, display: (0.0, 0.0, 3008.0, 1662.0), calculatedRect: (1504.0, 861.0, 1504.0, 831.0), resultRect: (1504.0, 861.0, 1504.0, 831.0), srcScreen: LG Ultra HD, destScreen: LG Ultra HD, resultScreen: LG Ultra HD
2026-08-19T14:59:55-04:00: AX sizing proposed: (2005.0, 1662.0), result: (1504.0, 831.0)
2026-08-19T14:59:55-04:00: AX position proposed: (1003.0, 30.0), result: (1003.0, 30.0)
2026-08-19T14:59:55-04:00: AX sizing proposed: (2005.0, 1662.0), result: (2005.0, 1662.0)
2026-08-19T14:59:55-04:00: rightHalf, display: (0.0, 0.0, 3008.0, 1662.0), calculatedRect: (1003.0, 30.0, 2005.0, 1662.0), resultRect: (1003.0, 30.0, 2005.0, 1662.0), srcScreen: LG Ultra HD, destScreen: LG Ultra HD, resultScreen: LG Ultra HD

Actions for log:
Positioned: Lower Right -> Positioned: Right (which cycles sizes as well as 'fills to top')

[rxhanson]

Sorry for the delay, thanks for reporting. I was able to reproduce it and will slate a fix for this coming release.

[patkujawa-wf]

I've experienced similar and had to downgrade to Version 0.96 (102) to get back to the old cycling behavior. I updated to the latest today but it was still doing this. I think I'm seeing it no matter where the windows are placed.