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
I have a component where the scrollable container has overflow: hidden, because its scroll position is controlled through code.
I need this because I have a virtualized table, where the header is a separate element of which the scroll position is synchronized with the body of the table through events.
This makes the position of the DragOverlay broken like this, as soon as the table is scrolled horizontally.
Unscrolled:
Scrolled:
Is there any solution to this?
From debugging the code I noticed that getViewRect is the function which determines the position of the element on the screen with the scroll offsets correctly but it is failing because of missing overflow property on the header container.
Why couldn't the code use getBoundingClientRect instead?
The weird thing is that the drag position seems to be actually determined correctly (the element is sorted into the position where the mouse cursor is), but ONLY the drag overlay is broken which tells me that dnd-kit should be able to handle this correctly.
The text was updated successfully, but these errors were encountered:
I have a component where the scrollable container has
overflow: hidden
, because its scroll position is controlled through code.I need this because I have a virtualized table, where the header is a separate element of which the scroll position is synchronized with the body of the table through events.
This makes the position of the DragOverlay broken like this, as soon as the table is scrolled horizontally.
Unscrolled:
Scrolled:
Is there any solution to this?
From debugging the code I noticed that
getViewRect
is the function which determines the position of the element on the screen with the scroll offsets correctly but it is failing because of missing overflow property on the header container.Why couldn't the code use
getBoundingClientRect
instead?The weird thing is that the drag position seems to be actually determined correctly (the element is sorted into the position where the mouse cursor is), but ONLY the drag overlay is broken which tells me that dnd-kit should be able to handle this correctly.
The text was updated successfully, but these errors were encountered: