Incompatibility with the new Chrome update (mobile only):

[jrosiapps-prog]

After extensive research and testing across multiple devices, I have confirmed a bug. Specifically on Chrome for mobile, following the February 3rd, 2026 update (version 144.0.7559.132), the select: function (event) { and eventDrop: function ({ event, revert }) { events are malfunctioning.

When dragging, the event triggers prematurely before the "drop" action occurs. The same issue happens with the select function: while selecting and dragging, the event is incorrectly fired before the finger is even lifted from the screen. I have tested this in other browsers, and they are all functioning perfectly.

[vkurko]

Thanks for looking into this issue. I believe this is a bug in Chrome. If you agree, please leave a comment here https://issues.chromium.org/issues/467952962

[vkurko]

@jrosiapps-prog I can't reproduce the issue in newly available Chrome 145.0.7632.45. Can you?

[jrosiapps-prog]

145.0.7632.45

My test devices haven't updated to version 145.0.7632.45 yet; I'm still on version 144.0.7559.132. You can even run free tests via Sauce Labs (https://accounts.saucelabs.com/am/XUI/#login/), as all their real test devices are also still running Chrome version 144.0.7559.132.

We know the issue is definitely with Chrome, so let's hope it has been resolved in this 145.0.7632.45 update.

Version "145.0.7632.45" only updated for PCs. The error only occurs on mobile devices that are still on version "144.0.7559.132".

[vkurko]

Version "145.0.7632.45" only updated for PCs.

I have Chrome 145.0.7632.45 on my mobile device, not PC.

[jrosiapps-prog]

Version "145.0.7632.45" only updated for PCs.

I have Chrome 145.0.7632.45 on my mobile device, not PC.

So that means the problem has been resolved in Chrome in this new version 145.0.7632.45 of chrome.

I haven't been able to get this new version working on any device, neither on my physical nor virtual test devices.

We're glad it's been resolved with the new update!

Thank you very much for sharing this excellent project. Your work is brilliant. Our team is actively maintaining it, and we will provide support whenever we encounter any technical incidents.

[vkurko]

I hope the problem doesn't recur, as it was first detected in version 143, then disappeared, and now it's reappeared in version 144 and disappeared in version 145. Very strange behavior.

Thank you for your kind words and for reporting the issue.