Android + Chrome@128 not working?

[inventorgg]

We use Pragmatic Drag and Drop for tree-style D&D throughout our product and have received a number of reports of drag and drop failing to 'start' a drag across multiple Android phones. It seems to change the state of the target item as if a drag had started, but doesn't create the floating item or properly show the indicator state.

We've been able to reproduce the report on a test device (against both our site and the examples site), and are not currently aware of a mitigation/fix. The issue seems to also occur with many (if not all of) the official examples available at https://atlassian.design/components/pragmatic-drag-and-drop/examples so we do not believe the issue is specific to our implementation.

The issue seems to have started a few days to a week ago, without any dependency or implementation changes on our end. Everything seems to work on a device with Chrome version 127.0.6533, so we believe it may be caused by a change in Chrome/Chromium version 128.

We're aware of the issue occurring with Chrome and Brave on these device configurations (and expect other chromium-based android browsers to be affected as well):

• Pixel 8 (Android 14, Brave 1.69.153 with Chromium 128.0.6613.85)
• Nokia 5.4 (Android 12, Chrome 128.0.6613.99)
• Samsung Galaxy A12 (Android 12, Brave 1.69.60 with Chromium 128.0.6613.114)

This screencap shows the issue on our site (loosely based on the tree example):
https://github.com/user-attachments/assets/c0c06f32-74cf-4f77-ab1d-ae8e668d9dab

This screncap shows the issue on the examples site:
https://github.com/user-attachments/assets/7b7c8e33-8c79-4807-b545-22a116aa4c50

We also received this video from an affected end-user. The first portion is Brave (Chromium v128), the second browser is Kiwi, which works as expected and uses Chromium v124.
https://imgur.com/bDMEOTe

[alexreardon]

I am currently unable to verify this issue as I don't have access to Chrome@128 on Android (Chrome@127 is the latest available to me).

If you have access to Chrome@128 on Android, can you please validate whether this minimal case works?

• Standalone: https://4q5x6d.csb.app/
• Source code: https://codesandbox.io/p/sandbox/drag-and-drop-for-andriod-4q5x6d

[alexreardon]

I've downloaded some newer versions of Chrome on my Android device. I have found no issues with with the standalone platform drag and drop example or with our pdnd board example on any of the versions I tried 🤔

• ✅ Chrome Beta@129
• ✅ Chrome Dev@130
• ✅ Chrome Canary@130

Tested on a Pixel 5 running Android@14

[inventorgg]

That's really strange. Just tried the minimal standalone demo on a Pixel 8 Pro (Android 14) with:

• Brave 1.69.153, Chromium 128.0.6613.85
• Chrome Canary 130.0.6693.0
• Chrome Dev 130.0.6683.0
• Chrome Beta 129.0.6668.20

It isn't working on any of those versions, but works on the exact same device with Chrome 127.0.6533.106.

[inventorgg]

Worked with some affected users and a test device to collect more info specifically about that standalone demo:

Working:

• Samsung A12 (Kiwi Browser v124)
• Samsung A22 (Brave v119)
• Samsung Galaxy S21 (Chrome v123)

Not working:

• Samsung A12 (Chrome Dev v130)
• Samsung A22 (Chrome Dev v130)
• Samsung Galaxy S21 (Chrome Dev v130)
• Samsung Galaxy S21 (Chrome Beta v129)

A21/A22 are on Android 12, Galaxy S21 is on Android 14.

[alexreardon]

Thanks so much for looking into this. Sounds like it's time to raise a bug with Chrome.

• @inventorgg can you please raise a bug with chrome? You have all the data so I think it would be best if you raise the bug. I personally have not been able to reproduce the issue yet.
• In your bug report, I think it would be clearest to lead with the standalone demo
• Can you please link the bug report here? I'll give input on the Chrome bug as needed

Cheers

[inventorgg]

Thanks for your help! Just created the issue at https://issues.chromium.org/u/0/issues/363930156

[alexreardon]

Thank you 🫡

[ColonelThirtyTwo]

I'm not able to interact with any of the examples on https://atlassian.design/components/pragmatic-drag-and-drop/examples/ using touch. Touches just scroll the page. I've tested it on Firefox and Chrome on Android, as well as Firefox's and Chromium's touch emulation on Linux.

Here's a video I took on Firefox for Android. I was attempting to drag the handles, and you can occasionally see one of them briefly highlight from hovering, but the screen scrolls instead of moving the items.

document_5098214068267779096.mp4

EDIT: Apparently FF not working is filed as #14 ... I'm frustrated that there's no touch event fallback.

[goodjobjohn]

+1
Chrome 128.0.6613.127
firefox nightly 132.0a1 (Build #2016043439)
android 12

[gibtree]

I'm not sure if this helps, but I can also reproduce this failure on Desktop on both Firefox and Chrome (on Linux) by using their Mobile emulation devtools. The touch events don't seem to be picked up at all by the examples page on a browser.

Version 128.0.6613.137 (Official Build) (64-bit) for Chrome.

Screencast.from.09-13-2024.09.46.45.PM.webm

[inventorgg]

Update for everyone here who isn't following the issue on the Chromium tracker - this issue has been resolved (sort of)!

The latest version of Chrome Canary (v132.0.6807.0) includes a fix for this issue. In our testing it seems to fully resolve the problem. Hopefully this fix will hit release versions of Chrome in the near future. If you don't see the issue fixed, please let the Chrome team know. Keep in mind that you need to be using Chrome Canary and may need to force an update, since the change is brand new.

Also, there seems to be a bit of confusion around Firefox. Firefox for Android does not support D&D and never has (this is noted on caniuse.com/dragndrop). Issues around D&D not working on Android FF are completely unrelated to this problem. There's no regression there since it was never supported, and it won't be available until the FF team implements D&D on Android.

With that said, this issue manifesting itself within Chromium-derivative android browsers (Brave, Vivaldi, etc.) is caused by this bug. We should see the issue resolve itself in those browsers as this fix is brought into stable Chromium and those browsers update their 'base' versions.

Thanks to @alexreardon for helping us track this down (and making PDND), everyone from the Chromium team who helped narrow down and resolve this (amazing work considering they had trouble reproducing it), and everyone here (as well as our users) who helped us confirm repros and narrow down specific versions that were affected.