Is your feature request related to a problem? Please describe.
The overall behavior and mobile support of sortablejs is great. However, the UX of having a partial opacity floating row doesn't mesh well with my app (it looks very messy with our items).
Describe the solution you'd like
I'd love to be able to implement a UX like this one (which does not work properly on mobile) where the element being moved is fully opaque and the drop position shows as a blank outline.
Describe alternatives you've considered
I tried styling the various classes exposed as well as setting the opacity of the item/clone elements in the onStart event, but this didn't work. From what I can tell reading the source styling is not an option because the opacity is set manually in JS.
Additional context
I'm new to SortableJS; apologies if this is entirely supported today and I just couldn't figure out the right path.
I'm using SortableJS through the React wrapper, but from my investigation it seems like the limitation is tied to the base library and not the React layer.
Is your feature request related to a problem? Please describe.
The overall behavior and mobile support of sortablejs is great. However, the UX of having a partial opacity floating row doesn't mesh well with my app (it looks very messy with our items).
Describe the solution you'd like
I'd love to be able to implement a UX like this one (which does not work properly on mobile) where the element being moved is fully opaque and the drop position shows as a blank outline.
Describe alternatives you've considered
I tried styling the various classes exposed as well as setting the opacity of the item/clone elements in the onStart event, but this didn't work. From what I can tell reading the source styling is not an option because the opacity is set manually in JS.
Additional context
I'm new to SortableJS; apologies if this is entirely supported today and I just couldn't figure out the right path.
I'm using SortableJS through the React wrapper, but from my investigation it seems like the limitation is tied to the base library and not the React layer.