Dragging sidebar splitter over Vue 2.0 node headers causes unintended node movement

[huchenlei]

Prerequisites

• I am running the latest version of ComfyUI
• I have searched existing issues to make sure this isn't a duplicate
• I have tested with all custom nodes disabled (see how)

What happened?

When dragging the sidebar splitter (resize handle) and the cursor passes over a Vue 2.0 node header, the node unexpectedly starts moving. This occurs with both the left sidebar and right sidebar splitters.

The splitter drag operation should not interact with or trigger node movement - these should be independent interactions.

Steps to Reproduce

1. Open a workflow with Vue 2.0 nodes (nodes using the new Vue-based rendering)
2. Start dragging either the left or right sidebar splitter to resize the panel
3. While dragging, move the cursor over a Vue 2.0 node header area
4. Observe that the node starts moving along with the splitter drag

Screen.Recording.2025-12-03.at.10.49.22.PM.mov

How is this affecting you?

Feature doesn't work as expected

ComfyUI Frontend Version

Latest

Browser

Chrome/Chromium

┆Issue is synchronized with this Notion page by Unito

[dosubot]

This is a known interaction conflict in the ComfyUI frontend. The root cause is that the sidebar splitter and Vue 2.0 node headers share overlapping pointer event regions. When you drag the splitter, pointer events can bubble to the node header, and the Vue node's drag logic may interpret this as a node drag—even though you only intended to resize the sidebar. This happens because the node drag handler listens for pointermove events globally and starts a drag if it sees a left-button move, even if the initial pointerdown wasn't on the node itself. If the drag start position isn't set by a node pointerdown, moving the splitter over a node header can cause the node to jump or move unexpectedly due to large deltas in the drag calculation see code details.

There isn't currently a mechanism to prevent node drag initiation during splitter drags, and recent updates to the splitter component did not address this see PR #6952. A possible mitigation would be to add logic that blocks node drag initiation when a splitter drag is in progress, or to ensure pointer events from the splitter do not propagate to node headers. For now, try to avoid moving the splitter directly over node headers as a workaround.

If you want to address this in code, look at adding a flag or state in the splitter component that disables node drag logic while the splitter is being dragged, or update the pointer event handling in the Vue node components to better distinguish between splitter and node interactions see related discussion.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}