Illustrator 30.2 | Partner Models, Firefly Boards, TIFF Export, Cloud Export, Scaling Enhancements and more

I’ve been able to fully reproduce the three-finger drag object jumping issue in Illustrator 30.x. This does not happen in version 29.x under the exact same interaction pattern, so this really looks like a regression.

When using three-finger drag on macOS to move an object, after releasing it at the intended position, there’s a noticeable delay (almost around ~1 second) before Illustrator visually restores the object to its normal “selected” appearance — meaning the bounding box and anchor highlights come back.

During that short window, the object looks like it’s already released. But internally it still behaves as if it’s in an active “grab” state. That’s the key part.

This extended post-release state seems to only happen with three-finger drag. It does not occur when using a mouse, and it does not occur with two-finger drag (force-click + move). Only three-finger drag shows this prolonged latent grab state.

To reproduce it in 30.x: move an object with three-finger drag, release it where you want it, and before the object fully returns to the normal selected appearance, just slightly move your finger again in any direction on the trackpad. The object immediately shifts again in that direction. Visually, it looks like the object “jumps” for no reason.

In 30.x this is reproducible 100% of the time for me. In 29.x, using the exact same steps, this behavior does not occur. That strongly suggests something changed in drag state handling or input finalization between versions.

You can actually observe the timing by watching how long it takes after release for the object to visually return to the selected state. With three-finger drag, that delay is noticeably longer compared to other input methods, and that visual delay matches the window during which unintended movement can still happen.

I suspect this may be underreported because many users still rely on a mouse, or use alternative drag methods. Heavy three-finger trackpad workflows might not be very common. I intentionally use trackpad-based workflows extensively, so I probably ran into this earlier and more consistently than others.

Speculating a bit, this feels related to drag state finalization timing, possibly differences in input event handling introduced in 30.x, or even how macOS gesture events are translated into pointer events. That said, since 29.x does not show this behavior, it seems more likely something changed inside Illustrator’s own drag or selection state logic.

As a temporary mitigation (not saying this is the correct architectural fix), one idea might be to introduce a short post-release suppression window. For example, when drag ends (mouseUp), record a timestamp t0, and for a brief interval after that — say t0 to t0 + N ms — ignore movement-affecting input events. Alternatively, suppress movement interpretation until the selection state is fully restored (like when the bounding box redraw is confirmed complete). That could prevent the visible “object jump” effect while the UI state finishes committing.

It’s probably not the cleanest long-term solution, but it might serve as a guard against this specific behavior.

I hope this makes the issue more concrete and easier to reproduce internally.

Thanks for taking the time to read through this.

P.S.
For clarity, this does not appear to be a general macOS three-finger drag issue. The same gesture behaves normally in Finder, on the desktop, and in other apps — once released, the drag state fully commits and no residual movement occurs. That makes it more likely this is specific to Illustrator’s drag state handling in 30.x, rather than the OS gesture layer itself. Which also suggests this should be fixable at the application level.