Edit: I have verified that this is a change in mobile Chrome’s handling of different data types when dragging. As usual, there is no documentation as to why the change was made or whether it was intentional.
I have just realized that drag and drop in Streams no longer works for me on Chrome 100.0.4896.79 on Android. Since I don’t regularly use Streams - especially not on mobile - I am unsure when this might have stopped working. I can confirm that drag and drop in the same version of Streams works on an older Android phone that has Chrome 99.0.4844.88.
If you use Streams on Android devices I would appreciate some feedback:
Does drag and drop still work for you?
What is your Chrome version number?
If it does not work, when was the most recent time that you can recall that it did work?
Latest Chrome on Android 10
Dragging: not working
Context: working
Firefox on Android
Dragging: not working
Context: working
Duck Duck Go on Android
Dragging: working
Context: not working
On my phone, with my thumbs, that bullet point is very difficult to hit to select context anyway. The dragging fail could be down to technique too. Maybe others can succeed but even where it is working on Duck Go it’s a fiddle. Can I suggest ‘press to select, long press to call up context’?
Apart from that negative quibble, streams is really fantastic - thanks Saq.
That is because it isn’t an intentional feature on mobile. Until Chrome 99 the context menu was never triggered successfully. That was why we ended up with a swipe gesture to trigger the context menu and the bullet point was never designed for long press on mobile. It seems the triggering of the context menu is related to drag no longer working.
The drag handle is actually much larger than the bullet point as it was optimized for mobile interaction, except for some reason the context menu is now also triggered and the drag aborts.
As a developer, it isn’t particularly enjoyable when browser changes break existing behaviour with no warning.
Edit: some clarification. If you see the background of a node turning grey on trying to drag, that isn’t the node being selected. That is what happens when a drag is started. However, the drag never proceeds nor ends properly so the grey colour persists.
I have verified that this is a change in mobile Chrome’s handling of different data types when dragging. As usual, there is no documentation as to why the change was made or whether it was intentional.
Chrome for Android 100.0.4896.88
drag and drop not working
DuckDuckGo browser 5.120.0 (not sure about the Chromium version)
drag and drop stopped working recently
Freedom Browser (Chromium-based) on Android 95.0.4638.50
drag and drop still working (but it’s a matter of time)
Firefox (Android) 99.2.0
drag and drop not working / has never worked
I’ve seen Stack Overflow posts about mobile FF’s implementation of HTML5 drag and drop which was problematic (I can’t find them anymore) and was wondering if there was a way to get around that by changing things in the TW core that would finally enable drag and drop in Firefox (Android)?
I know we have the Mobile Drag and Drop Shim Plugin, which enables d&d on FF and probably on Chrome as well but it’s been hit and miss for me – dragging and dropping on FF works with it but on drag the entire page is also scrolled, so… UX is not great at all.
Referring to Saq’s github issue, is this new Chrome “bug” or braking change in any way related to the way things have been working in Firefox? If it is, could this perhaps be addressed as well or would a separate issue be needed? Or maybe that’s something we have no control over at all because it’s up to Mozilla to fix?
