New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to drag and drop on mobile using React Portal #2111
Comments
I ran into the same issue. After some digging the problem is probably with dissapearing (moved to portal/clone) draggable item after drag start. First touch on drag start scrolls the whole page/list, second touch on draggable item drag the item correctly. The same problem is on the following stories:
We can simulate this simply on Windows Chrome device emulation, or by opening stories on Android Chrome (iPhone has the same issue). |
I tried old versions and it works in version: "12.0.0-beta.10" |
I checked the version and in 12.0.0-beta.11 was rewritten code for detection of dragging element. |
I can confirm this behaviour works on 12.0.0-beta.10 and not anything above! Thanks @Merynek, I didn't know how else to fix this problem |
Here are the diffs between the versions: v12.0.0-beta.10...v12.0.0-beta.11 |
Did you find a solution or hack for this bug? |
same issue here! is the current solution to stick with thanks! |
Still having the same issue. Any update would be great! :) |
@nmauersberg, @maxsupera, and anyone else still looking for a fix, years later: I fixed the issue by cloning the default touch sensor and adding back in the logic they took out with the 12.0.0-beta.11 change. Having both sets of logic side by side should make all scenarios work: Steps:
Then import it into wherever your DragDropContext lives and use it like so:
|
I cant dragging with items on mobile when I use portals.
You can check this on your own examples.
I found out that you solved this in version 12.0.0-alpha.7 so mby its regression.
Relase: #1317
Issue: #582
Example: https://react-beautiful-dnd.netlify.app/iframe.html?id=portals--using-your-own-portal&viewMode=story
The text was updated successfully, but these errors were encountered: