Here was my reply - typing this up for the 2nd time...

Yes - this is what I did to work around the issue -

.sortable-item-dragging { z-index: 9000 !important; }

It works.

Yesterday, I noticed another issue. I have enabled the following:

data-mdb-block-x-axis = true

And that works as well. However, after dragging and letting go of the mouse button, the dragging item jumps to where my mouse cursor is, and then does the final animation to settle into the spot it was dragged into, as if the axis block was turned off right before starting the final animation. This is very jarring and looks broken. Please fix this as well.

Ugh - I just typed up a long reply here and it asked me to log in, which I did, and after doing so this site completely threw away my reply. :-\

I'll add this to our to-do list. We will fix it as soon as possible. As a workaround you can add styles to increase the z-index of the .sortable-item-dragging element

Investigating further it seems like the culprit is MDB is placing the "dragging" class on the drag handle instead of the drag container. The "dragging" class is what sets the z-index. The fix would be to always put the "dragging" class on the container, never on the handle.