Due to the issue with Chrome 62 then its forced us to upgrade from 1.5.1 to 1.7.0 however something has broken and I'm not sure where.
After upgrading to 1.7.0 the dragging region is much too large and whilst the insert/drag functionality is working it looks visually terrible as the size is including some invisible DIVs as well as what looks like a -ve vertical offset.
However if we set the forceFallback flag to TRUE then it works perfectly as before.
Any ideas? Don't really want to leave the forceFallback in permanently.
Thanks
Kate
:[ no ideas
Evething ok with 1.6.1 version and Chrome 62.
Honestly, do not understand what you're saying :[
I do not see a problem.
On 47de7844aa88556133384211620ada8a7dea3f65 (yesterday master before 1.7.0 release) there are errors
sortable.self-9b62ef77c7aa4c93f48346c4b63a6bcaa881b6d9f56eb119ea389f09b8c6b860.js?body=1:1502 Unable to preventDefault inside passive event listener invocation.
when dragging in chrome device emulator mode.
Rechecked now and everything works perfectly for me.
I still do not understand what is wrong?
For example http://recordit.co/DfI3VG3jKi
I've reverted to V1.6.1 and removed the forceFallback and its all working OK with this version/config. Will see if I can record an animation of the V1.7 behaviour and post later.
I've recorded two snippet below, first with 1.7 then with 1.6.1, apart from swapping the Sortable version between the clips there are no other changes:
V1.7.0 - http://recordit.co/iXsJdaxRH5
V1.6.1 - http://recordit.co/ESAi4EEwu6
forceFallback not used.
Chrome OSX - Version 62.0.3202.75 (Official Build) (64-bit)
I have the same problem. sometimes the whole div is being dragged (with all the other images on the list) and sometimes the dragged image is a little larger than it should and contains what was around that image.
Setting forceFallback to true works but I would love to know what is it used for exactly...
I needed to get an update because something was not working anymore with jQuery 3.1.1
Now using Google Chrome, jQuery 3.2.1
Can somebody create an example on jsbin.com (draft)?
@KateWilkins , @YovavGad?
1.6 version and Chrome 62, I have the same problem,but upgrade from 1.6 to 1.7.0 ,fixed it
Im having issues as well with Chrome 62
I have the same issue with version 1.7.0. When I've rollback to the 1.6.1 all work correctly.
For some people 1.6.1 but for others 1.7 is working?
Most helpful comment
1.6 version and Chrome 62, I have the same problem,but upgrade from 1.6 to 1.7.0 ,fixed it