🐞 Window Snapping Half-Screen Regression in v1.4.3 (1716)

[AlejandroVolkova]

Bug Description

After upgrading to Version 1.4.3 (1716), I encountered an issue with Window Snapping. Specifically, when attempting to snap a window to half of the screen, Loop now suggests unexpected positions instead of the intended half-screen layout. In previous versions, this functionality worked consistently as expected, but since this specific update it no longer behaves correctly.

Affected Scope

User interface

Steps to Reproduce

1. Upgrade to Version 1.4.3 (1716).
2. Open any application window.
3. Attempt to snap the window to half of the screen (e.g., dragging to the left or right edge).
4. Observe the suggested snapping positions.

Reproducibility

Often (≥70%)

Expected vs Actual Behavior

The window should snap cleanly to half of the screen (left or right side), as it did in previous versions.

Screen Recordings / Screenshots

Half-Screen.Regression.mp4

Severity

Critical (major functionality broken)

macOS Version

macOS Tahoe 26.4 RC

Loop Version

Version 🧪 1.4.3 (1716)

Did You Try the Development Build?

Yes

Additional Context

No response

Final Checks

• My issue is written in English.
• My issue title is descriptive.
• This is a single bug (multiple bugs should be reported individually).
• I have looked to see if this is a duplicate of another bug report.
• I can help with further investigation.
• I can help with developing a fix for this issue.

[AlejandroVolkova]

@mrkai77 Could I please get a download to the previous build 🙏🏻? I need to downgrade because to me it's unusable, but I would like to avoid the stable release since the previous build was super solid.

[SenpaiHunters]

Hey, @AlejandroVolkova, this isn't actually a bug; it's a part of the new window snapping design introduced in PR #1068. You can see all of our builds and downloads at https://github.com/MrKai77/Loop/actions/workflows/dev-build.yml, and manually update or downgrade as needed. However, every 12-24 hours, it will ask you to update to the latest version. I did say to Kai that we may want to put the old code and method behind a defaults flag for those who are used to the old snapping like myself, but it was decided against that in favor of how it works now. There may be UI changes later, but do give your feedback.

[AlejandroVolkova]

Hey @SenpaiHunters , I see, thank you very much, the link is exactly what I needed. After being a Loop user for several years, I believe this change is not an improvement but rather a significant step back in terms of user experience, especially for long-time users of Loop, as it introduces unnecessary friction. As I’ve mentioned before, I come from using Yabai and have thought deeply about this topic, so I have a strong opinion on what makes the best window distributions on macOS built‑in displays. In my view, the previous design of Loop’s window snapping before this modification was simply brilliant due to its simplicity and practicality.

I also don’t think Loop should prioritize external workflows over the default one it already provides, because that’s where its true value lies, and it was excellently designed from the start. With this modification, unfortunately, I don’t see myself recommending Loop to “regular” users, since it only adds more complexity and friction, when most users realistically prefer simplicity.

I do understand that some users may want this type of functionality, particularly on external monitors or because they have muscle memory from other software. However, in my opinion, this should be an optional feature for those who need it, not a replacement for the original functionality that made Loop such an outstanding tool. Long time users should not be pushed into adopting a new workflow, especially when the original one was already highly effective and user‑friendly.

[mrkai77]

Maybe we should only enable thirds on the primary axis? Previously, thirds didn't work on vertical monitors (only halves did) which is why this change was made. This "primary axis" method would instead make it so that, on a 16:10 display, the 16 side could get thirds while the 10 side stays limited to halves, so that the layout doesn't get too crowded.

[AlejandroVolkova]

I think it makes sense to me!

[mrkai77]

Sorry for the delay in getting this fixed, it’ll be resolved in the next development release :)