Bug
To be able to drag and drop items on mobile.
The items are marked as draggable, but can't be dragged.
Go to https://codesandbox.io/s/3465m7xmw6 and open mobile emulation.
React are you using?16.3
react-beautiful-dnd are you running?7.1.3
Chrome
We'll track as a part of #567
Here is an independent example that shows of the behaviour: https://codesandbox.io/s/nr75vkklnm
This example does not use react-beautiful-dnd at all. It looks like moving something into a portal after a touchstart stops any window touchmove and touchend events from firing.
Here is an example that uses a React.Portal but it shifts the component into a component before a touch start. That works fine. https://codesandbox.io/s/v54x54vp5
I will create an issue on the React project to track this.
Unfortunately given that this issue is with React.Portal itself we are unable to action this directly
React issue created: https://github.com/facebook/react/issues/13113
I'll update the docs to let people know about this issue
This is surpising as I thought I tested using portals on mobile... very confusing.
Oh well, I am able to reproduce it outside of this library so for now we cannot really do too much :(
I have created a warning in the docs: https://github.com/atlassian/react-beautiful-dnd/pull/583
This is also caused by the removing of the existing node and re-creating of one. It looks like there could be a workaround which I will explore: https://github.com/facebook/react/issues/13113#issuecomment-410311889
Hello,
any news about the problem ?
i have not digged into this one yet
Any chance to use this solution https://github.com/facebook/react/issues/13113#issuecomment-438901454 ?
This might be fixed as a part of our event changes for #1293
I am looking into this as a part of #1293
I can confirm I have found a workaround for this as a part of #1293. The new pattern also works with dragging clones which is needed for virtual lists
/cc @TrySound
Awesome
Shipping in 12.0 #1317
Fixed in 12.0.0-alpha.7
Most helpful comment
This is also caused by the removing of the existing node and re-creating of one. It looks like there could be a workaround which I will explore: https://github.com/facebook/react/issues/13113#issuecomment-410311889