Looks like nodeRef causes jittery movement when the handle is not a direct ancestor. For example, using the nodeRef example from the README and adding a div wrapping the target causes this issue.
We're updating draggable modal windows to use nodeRef props to avoid the console warning about findDOMNode being deprecated. Previously, we had handle set to a DOM class name and that exact class name assigned to an element inside the element.
<Draggable nodeRef={dragRef}>
<div>
<header className={clsx(styles.header, styles[uiVariant])} ref={dragRef}>/* content */</header>
</div>
</Draggable>

With the handle approach, the movement when dragging and item was smooth and we had no issues. With the nodeRef, it's incredibly jittery. We normally have bounds and onDragStart methods but I removed those for testing and the jitter persists.
Looks like
nodeRefcauses jittery movement when the handle is not a direct ancestor. For example, using the nodeRef example from the README and adding adivwrapping the target causes this issue.We're updating draggable modal windows to use
nodeRefprops to avoid the console warning aboutfindDOMNodebeing deprecated. Previously, we hadhandleset to a DOM class name and that exact class name assigned to an element inside the element.With the
handleapproach, the movement when dragging and item was smooth and we had no issues. With the nodeRef, it's incredibly jittery. We normally haveboundsandonDragStartmethods but I removed those for testing and the jitter persists.