Custom Combo select box becomes disabled after running Refresh Node Definitions

[fappaz]

Prerequisites

• I am running the latest version of ComfyUI
• I have custom nodes enabled

What happened?

The choice select box for the Custom Combo node becomes disabled when I trigger Refresh Node Definitions, so I cannot switch to another option. See video below:

custom-combo-issue.mp4

A temporary workaround is to switch tabs in ComfyUI, that seems to unblock the select box and we can choose an option again.

Steps to Reproduce

1. Add a Custom Combo node to the workflow
2. Add at least 2 options in the node
3. Hit the R key (or menu > Edit > Refresh Node Definitions)
4. Notice how you can no longer select a different option in the combo
5. Switch to a new tab in ComfyUI, then switch back to your workflow to re-enable the select box.

How is this affecting you?

Visual/UI issue only

ComfyUI Frontend Version

1.42.15

Browser

Chrome/Chromium

Console Errors

Logs

Additional Context

Tested with frontend 1.43.1 too, same issue.

System Info

OS: win32
Python Version: 3.11.6 (tags/v3.11.6:8b6ee5b, Oct 2 2023, 14:57:12) [MSC v.1935 64 bit (AMD64)]
Embedded Python: true
Pytorch Version: 2.9.0+cu128
Arguments: ComfyUI\main.py --windows-standalone-build --disable-all-custom-nodes
RAM Total: 31.36 GB
RAM Free: 19.1 GB
Templates Version: 0.9.68

Devices

• cuda:0 NVIDIA GeForce RTX 3080 Laptop GPU : cudaMallocAsync (cuda)
  VRAM Total: 8 GB
  VRAM Free: 6.94 GB
  Torch VRAM Total: 0 B
  Torch VRAM Free: 0 B

┆Issue is synchronized with this Notion page by Unito

[dosubot]

This looks related to how the Custom Combo node manages its options via a Vue shallowReactive array [1], which gets overwritten during the "Refresh Node Definitions" process.

The root cause appears to be that Custom Combo doesn't implement a refreshComboInNode() method [2], so it falls through to the default refresh logic which directly assigns widget.options.values from the reloaded node definitions [3]. Since Custom Combo has no standard input spec, this overwrites the reactive array with undefined or a plain value, breaking Vue's reactivity and effectively disabling the select box.

This is the same pattern as PR #11815 for Primitive nodes [4], where the refresh process blanks out combo dropdowns by overwriting options without null checking.

A fix would be to add a refreshComboInNode() method to the Custom Combo node extension that returns early (or rebuilds options from sibling option widgets), preventing the default refresh logic from clobbering the reactive state.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.