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
Have not had a chance to create a Sandbox yet, but just reporting in case there is a trivial workaround.
I have a use case of having a table with sortable rows, which each row containing another table with sortable row. I am using drag handle (data-movable-handle).
In this case, I see the issue that dragging one row from the nested table sometimes drags the parent row from the parent table. Would there be an easy workaround for fixing this?
Maybe providing the ability to customize the "data-movable-handle" property name so there is no conflict between the 2 components?
The text was updated successfully, but these errors were encountered:
Have not had a chance to create a Sandbox yet, but just reporting in case there is a trivial workaround.
I have a use case of having a table with sortable rows, which each row containing another table with sortable row. I am using drag handle (data-movable-handle).
In this case, I see the issue that dragging one row from the nested table sometimes drags the parent row from the parent table. Would there be an easy workaround for fixing this?
Maybe providing the ability to customize the "data-movable-handle" property name so there is no conflict between the 2 components?
The text was updated successfully, but these errors were encountered: