🐞 window jump when dragging on the secondary (external) display

[Ender-Wang]

Bug Description

I have seen a weird behavior when I drag app windows when I am connected to a second display.
When I drag a window on the external display(secondary display) around (drag it within the screen, not to the main display), the app jumps to the bottom of the main screen (mac display), I am not sure if it's a bug related to Loop or macOS 15.7. Since Loop is the only window manager app I have on this mac, here I am. Noticed this recently when I work on the second display, multiple times a day.

Steps To Reproduce

• Connect mac to a second display, mac screen set to main screen,
• drag a window on the secondary display

Expected Behavior

The app should not jump to the other display.

Actual Behavior

App window jumps.

Screenshots

No response

macOS Version

15.7

Loop Version

v1.3.0

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 can help with fixing or developing this issue (tick if you can help).

[cipher-shad0w]

Can you try updating to the latest development version (1.4.0) to see if this issue persists? You can enable the development version in Loop's "About" tab.

[Ender-Wang]

Ok, I will report back in a few days. Thanks.

[Ender-Wang]

Can you try updating to the latest development version (1.4.0) to see if this issue persists? You can enable the development version in Loop's "About" tab.

It's much less frequent, but worse when it happens. Happened once in the morning, but the same jump happens, the window glitches a bit, then jumps to the other screen. I will close Loop for a while, just to eliminate its system bug.

Edit:
Do you recommend disabling those while using Loop? I just disabled those. Maybe there's some sort of conflicts going on with these enabled.

[cipher-shad0w]

It is possible that this is the cause. I will reproduce the bug in the next few days and can tell you more about it then. Thank you for creating the issue

[cipher-shad0w]

Do you have "use macOS window manager when available" enabled?

[Ender-Wang]

Do you have "use macOS window manager when available" enabled?

Nope, it's always off.

[Ender-Wang]

In case settings matter, this is mine.

Loop Keybinds.json

[mrkai77]

@Ender-Wang one more test, could you try running a version of Loop before 1.3.0, like 1.2.0, to check if the bug existed back then? If you already had that version installed a few months ago, it might help confirm whether this is something new in macOS 15.7 that’s causing issues with Loop.

[Ender-Wang]

@mrkai77 I have had this issue before macOS 15.7, on 15.6, etc, but I will give it a try with v1.2. Will report back soon.

[Ender-Wang]

@mrkai77 I've been using it for a few days, and I haven't encountered any issues with v1.2. No glitches at all. macOS 15.7.1, a M3 family mac.

[Ender-Wang]

@mrkai77 Hmm, I've got to take it back. I just noticed the exact same problem multiple times today (because I don't drag the window that much, using keyboard shortcuts 99% of the time), on v1.2, macOS 15.7.1. Recently, I got a third monitor(it should not matter, cause it also happens on a two display setup), and the Mac display is still the main one.

• Besides, I found a pattern on triggering it on my end 100%:
  • If the window is not maxed out (edge to edge), the glitch does not appear (most of the time, ~90%).
  • If I maxed out the window using Loop (also it's the only window manager I have), then drag it on the main display, the window restores to its previous size, which is expected behavior.
    • But when I maxed out the window on a secondary display(I got two displays connected, I mean on any of them), the jump happens 100%, it(the title bar of the window) jumps to the bottom edge of the secondary display or to the main screen bottom edge.
  • If I do not max it out, dragging on the secondary display also glitches sometimes.

Btw, screen arrangements of my setup is, it might help to pinpoint the root cause. If you have a log built in, it would be great for troubleshooting. I'd like to provide logs on Loop, if you know how.

[mrkai77]

Thanks for the info @Ender-Wang! I was able to reproduce the bug with your instructions, will take a look and try to fix it.