Signal reaching clickDistance threshold? about d3-drag

[GordonSmith]

@Herst - to workaround losing your click event, tweak how "raise" works to not move the "drag" node, but rather move all its siblings:

            //  Safe Raise - does not interfere with current click event  ---
            const dragNode = /* the DOM node being dragged during "dragstart" event */
            let nextSibling = dragNode.nextSibling;
            while (nextSibling) {
                target.parentNode.insertBefore(nextSibling, dragNode);
                nextSibling = dragNode.nextSibling;
            }

[Herst]

Demo demonstrating my current solution: https://bl.ocks.org/Herst/3d486648556a3eee60442da977022fd1

[mbostock]

Would it be cleaner to not call event.preventDefault() on the mousemove event until the click distance threshold is crossed? Then you could check event.isDefaultPrevented to test.

[Herst]

I guess this could work. I wonder if this would have any (good or bad) side effects concerning #9:

It’s a Chrome bug that calling mousemove.preventDefault prevents text selection, drag-and-drop, and scrolling (see issue 485892). The mousemove event is defined as having no default action.