[ Vue nodes ] When I try to connect to a widget, it only connects to the first connectable widget.

[JorgeR81]

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 I try to connect to widget, it only connects to the first connectable widget.

Steps to Reproduce

Try to connect an INT node to the batch_size widget, in the Empty Latent Image node.
It only connects to the first widget ( width ).

To make the connection, we need to connect to all widgets above.

And then remove the connections above. 

---

I also tried the KSampler node, with INT and FLOAT nodes, with the same results.

Here, I'm trying to connect to denoise, but it only wants to connect to cfg. 

Only after cfg is connected, I can connect to denoise.

How is this affecting you?

Feature doesn't work as expected

ComfyUI Frontend Version

1.32.0

Browser

Chrome/Chromium

Console Errors

Logs

Additional Context

No response

┆Issue is synchronized with this Notion page by Unito

[dosubot]

This is the current, intended behavior in the Vue-based ComfyUI frontend: when you connect an output to a node with multiple compatible widgets, the connection logic automatically attaches to the first eligible widget it finds. There is no UI affordance to select which widget to connect to if several are compatible—the system always picks the first one. To connect to a widget further down (like batch_size), you have to fill the widgets above it first, then remove those connections if you want only the lower one connected. This matches what you’re seeing and is a limitation of the current implementation.

The relevant logic is in the frontend code, where the function responsible for connecting outputs to widgets (findConnectableWidget) simply returns the first compatible widget. There’s no mechanism yet for user selection among multiple options, but the code is modular enough that this could be improved in the future.

Recent pull requests and bug fixes have focused on subgraph connection handling and disconnection logic, but none address this specific widget selection behavior. There are no known workarounds other than the one you described (connecting to all widgets above, then removing those connections) source.

If you need to connect to a specific widget, you’ll need to use the current workaround until the frontend adds a selection UI for this scenario.

To reply, just mention @dosu.

---

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

[jovan2009]

This is the current, intended behavior in the Vue-based ComfyUI frontend: when you connect an output to a node with multiple compatible widgets, the connection logic automatically attaches to the first eligible widget it finds. There is no UI affordance to select which widget to connect to if several are compatible—the system always picks the first one.

I'm sorry to laugh at the bot and at the situation but this is like putting the next meal in your body in the first hole available, to keep the language clean. 🤣
I know it's hard work involved developing this and it's not laughing matter but I couldn't resist.

[AustinMroz]

Would like to confirm before I start diving into a fix: I can connect to widgets other than the first if I hover very carefully over the connection dot. Is increasing the valid drop area to the entirety of the widget sufficient, or is there an additional issue I'm not able to reproduce?

[JorgeR81]

Yes, you're right !

We can connect, if we place the cursor exactly in the target slot.