- Issue created by @purencool
- 🇨🇦Canada jeremylichtman
The fallbackOnBody has to do with the theme you're using. I think we need a fallback (i..e where the element goes back to on failure), but possibly we need something around the naming of the container. Or switch to fallbackOnParent. Or some such.
I'll do the controller change now. Will commit on dev for now, as it looks like there's other fixes coming.
- 🇦🇺Australia purencool
So what change do you make so I can retest the issue?
- 🇨🇦Canada jeremylichtman
Changes are in recent tags. The controller change was the one you suggested (all instead of post).
- 🇦🇺Australia purencool
Could this be used in the code instead. As I am not sure how this can be fixed.
https://github.com/SortableJS/Sortable/pull/2245/commits/ee3cecef0346ea0...
getFallbackParent: null, // Getter function that returns the parent for the cloned DOM Element
- 🇨🇦Canada jeremylichtman
I intentionally built this to use the internal Drupal js library. The goal was a module that had no other dependencies required to install it.
I've removed the fallback option in 1.0.x for now. The other option appears to be in an open merge request on Sortable, and probably won't be part of the version included in Drupal for a while yet.