v1.26.8 v1.26.9 v1.27.0 causing incorrect mouse/node detection

[CoreyCorza]

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?

In frontend v1.26.8 a bug has been introduced causing incorrect mouse coords regarding node detection.

SANITY CHECK: when the mouse moves within the border of the node - the mouse turns to a cross.
When the mouse moves outside the border of the node - the mouse turns to an arrow.
Ground truth behavior.
https://github.com/user-attachments/assets/46f55858-ed10-49d0-90f6-340bd61352b9

BUG: Suddenly appears.
Now the top of the node is offset inside the node?
The top of the node, is no longer the top of the node.
The top of the node is now inside the node.
There is a large portion at the top of the node where it cannot be interacted with.
https://github.com/user-attachments/assets/f43a69a9-df75-480f-94b5-ab15b5bc8f1f

Steps to Reproduce

1. Hold alt to duplicate a node
2. Sometimes, but mostly always, depending on the zoom factor of the viewport, an extremely large offset from the top of the node occurs - or a small offset at least
3. Pay close attention.

ComfyUI Frontend Version

v1.26.8 , v1.26.9

Browser

Chrome/Chromium

Additional Context

This is not only causing mis-clicks when trying to move native nodes. But also causing incorrect mouse click detection for custom nodes.

┆Issue is synchronized with this Notion page by Unito

[dosubot]

There is a confirmed bug in recent versions where duplicating a node with Alt causes the node's interactive area to become offset, especially at certain zoom levels. Recent pull requests have addressed related issues with Alt+drag duplication, particularly for subgraph nodes and widget ordering, but not the specific mouse coordinate offset you described. The core logic for node duplication, mouse coordinate transformation, and hit detection is handled in the graph and canvas code, and recent changes in these areas may have introduced this regression. No open issues or documentation directly address this exact bug yet, but the recent fixes for Alt+drag duplication in subgraph nodes suggest this area is under active development and may be related to your issue. If you need to investigate further, reviewing the recent changes in node duplication and coordinate handling logic would be a good starting point.

References:

• Widget order and value issues after Alt+drag duplication
• Recent PRs fixing Alt+drag duplication for subgraph nodes

To reply, just mention @dosu.

---

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

[CoreyCorza]

This problem is so bad and exacerbated in v1.26.8 / v1.26.9 that I cant even move reroute nodes

[CoreyCorza]

v1.26.7 <---------------- problem does not exist.
v1.26.8 / v1.26.9 / v1.27.0 ----------> problem does exist

[KrsityKu]

I've updated to v1.27.0 earlier today, and I also have ran into this issue, for me it seems to happen as follows:

1. Select a node by clicking on the node's title bar
2. Move your mouse across the title bar from left to right
3. At around half way point, the cursor changes from + to regular cursor, and the node cannot be dragged from that area. It only can be dragged from the first part that has the + cursor.

Doing the same over a node that is not selected, behaves correctly.

[loz2754]

I too have experienced mouse issues since 1.26.8, similar to what is being described. Though it seems to me that the toolbox menu is somehow larger than it appears, and I have to click quite a way away from it to restore click and drag motions. Also double-clicking to rename the node title sometimes cause the text in an unrelated node to be highlighted instead of the node title text.