node 2 design

[comfy-pr-bot]

Custom Node Testing

• I have tried disabling custom nodes and the issue persists (see how to disable custom nodes if you need help)

Expected Behavior

node 2 for me its a bug

if i hit a number with a point "1,2"
it is not marked like before and if i must press and move the mouse to mark or if i double click its only marked until the "," and i must click 2times...

...
next
if i click a field that has a option to chose several items in a column one below the other..
this is in background so if a node below i can no see all

who has tested that? you want a guy that pretest alpha versions?

---

This issue is transferred from: comfyanonymous/ComfyUI#11126

Original issue was created by @kalle07 at 2025-12-05T18:36:15.000Z

┆Issue is synchronized with this Notion page by Unito

[dosubot]

Both issues you described are known bugs in the ComfyUI frontend:

• The numeric input field bug—where clicking or double-clicking a number with a decimal point only partially highlights the value, and direct decimal entry is unreliable—is due to the switch to the PrimeVue InputNumber component. This widget currently does not support direct decimal input or math expressions, especially in Chrome/Chromium. The recommended workaround is to calculate your value externally and paste it into the field. There is no evidence of a planned fix or restoration of the old math input feature at this time (source, source).

• The dropdown menu rendering issue—where multi-select dropdowns appear behind other nodes—is related to CSS stacking context and z-index handling. The dropdown uses a Popover with a high z-index (z-50), but if other nodes have higher stacking or transform contexts, the menu can still be obscured. The codebase includes a composable (useTransformCompatOverlayProps) to help overlays render correctly within transformed parent elements, but this does not always resolve the issue (source, source).

Both bugs are not caused by custom nodes and are present in the core frontend. There is no official workaround for the dropdown stacking issue, but you may have better results by adjusting node positions or using a different browser. For the numeric input, pasting values is the only reliable method for now.

Testing and QA for these UI components is ongoing, but regressions have occurred due to the migration from LiteGraph to Vue/PrimeVue. Maintainers are aware of these limitations, but there is no timeline for fixes (source).

To reply, just mention @dosu.

---

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