You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can create a test case showing the problem, using a piece of html/js that incorporates the SortableJS library. If I can provide that, can you help me debug how to get it working? cheers.
Reacted by Tomasz Szczęśniak-Szlagowski, Ryan Bates and Yulian Tarantiuk
interesting, thanks @swanson for getting my attention to your change. I'd love to see the file where you're successfully pulling this off if you have something you'd be willing to share..
I tried switching drivers to apparition but in the timebox I had allowed, I couldn't even get apparition to start up - it just hung at me, so I switched by to cuprite and @wip-ed my test.
Had you made any progress on this? Is there any way I can help?
Thanks for replying .
Maybe we are talking about different versions of gem, but in the current one (cuprite (0.14.3)) you cannot set arguments for the drag_to method.
As described in #182 -- you will need to use forceFallback: true option in SortableJS and also pass in an option for steps in drag_to (I used 10).
Hi, @swanson !
I made a small monkeypath (as I only need one drag_to method) and can confirm that everything works as expected !
Thanks, I will wait for the release with MR enabled.
Just hit up against this also. Is it that Sortable.js is looking for different pointer events? Perhaps it's looking for pointer events and not mouse events? Using the fallback option seems to be a less than optimal solution since it affects actual users.
Activity
route commentedon Dec 5, 2021
Sure go ahead and I'll help
swanson commentedon Jan 8, 2022
#182
jubishop commentedon Jan 8, 2022
interesting, thanks @swanson for getting my attention to your change. I'd love to see the file where you're successfully pulling this off if you have something you'd be willing to share..
pedantic-git commentedon Oct 12, 2022
Hi @route - I'm just bringing this issue back to life because I've also experienced this same trouble with SortableJS today. My code is open source and my test is here: https://github.com/fishpercolator/name.pn/blob/main/features/signup_and_edit_profile.feature#L242
I tried switching drivers to apparition but in the timebox I had allowed, I couldn't even get apparition to start up - it just hung at me, so I switched by to cuprite and
@wip-ed my test.Had you made any progress on this? Is there any way I can help?
sergey-arkhipov commentedon Sep 10, 2023
Is there any progress on this issue ?
drag_to does not work with SortableJS.
Direct use of Ferrum methods doesn't work either
Is any workaround to do that ?
swanson commentedon Sep 11, 2023
As described in #182 -- you will need to use
forceFallback: trueoption in SortableJS and also pass in an option forstepsin drag_to (I used 10).sergey-arkhipov commentedon Sep 11, 2023
Hi, @swanson !
Thanks for replying .
Maybe we are talking about different versions of gem, but in the current one (cuprite (0.14.3)) you cannot set arguments for the drag_to method.
The code from the current gem
Accordingly, the test execution error
swanson commentedon Sep 12, 2023
It is there on the
mainbranch: https://github.com/rubycdp/cuprite/blame/main/lib/capybara/cuprite/node.rb#L162Maybe a release issue?
route commentedon Sep 12, 2023
The new release is going to happen soon
sergey-arkhipov commentedon Sep 14, 2023
Hi, @swanson !
I made a small monkeypath (as I only need one drag_to method) and can confirm that everything works as expected !
Thanks, I will wait for the release with MR enabled.
brendon commentedon Feb 5, 2025
Just hit up against this also. Is it that Sortable.js is looking for different pointer events? Perhaps it's looking for pointer events and not mouse events? Using the fallback option seems to be a less than optimal solution since it affects actual users.
ryanb commentedon Feb 20, 2025
@brendon
I recommend setting the
forceFallbackoption only ifRails.env.test?. I agree it still isn't ideal but at least it only affects test env.Also I found I needed a higher
stepscount otherwise the test would flake about 20% of the time. I went withsteps: 20.brendon commentedon Feb 20, 2025
Thanks @ryanb, for now I've removed those tests. That is a good idea though around forcing the fallback option only in test.
Once day if I have some time I'll try to troubleshoot this a bit more :)
frenkel commentedon Aug 21, 2025
@ryanb Thanks,
forceFallback: trueandsteps: 20seem to make it reliable for me!