Regression: mouse clicks intermittently not registering on node widgets in ComfyUI 0.27.0 / frontend 1.45.20

### Custom Node Testing

- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Expected Behavior

Mouse clicks on ComfyUI node widgets should register consistently on the first click when clicking directly on the visible control.

Expected examples:

* Clicking a dropdown field should open the dropdown.
* Clicking a numeric/text field should focus the field.
* Clicking seed, steps, cfg, sampler, scheduler, or similar widget rows should reliably select or activate the intended control.
* Node widget hitboxes should match the visible UI controls.
* The same click behavior should be consistent across normal node interaction.

In my previous ComfyUI install on the same system, mouse clicks register normally.

### Actual Behavior

In ComfyUI 0.27.0 with frontend package 1.45.20, mouse clicks on node widget controls intermittently do not register.

The cursor appears to click directly on the intended control, but the UI sometimes does not respond. Repeated clicks may eventually work. This is most noticeable when interacting with widgets inside nodes such as KSampler Advanced, including dropdowns, numeric fields, seed/steps/cfg fields, and other widget rows.

The workflow canvas remains visible and ComfyUI does not crash. This appears to be a frontend/UI interaction issue rather than a backend generation/runtime issue.

I tested a previous ComfyUI install on the same system, ComfyUI 0.16.3 with frontend 1.39.19, and the issue does not occur there. In that version, clicks register normally.

Attached videos:

https://github.com/user-attachments/assets/e9693d0b-4d0c-4bc1-9e65-d0f7ce7a9ae3
https://github.com/user-attachments/assets/c9817fac-a198-4afe-8e19-2a78fa099a9d

1. ComfyUI - clicks not registering - ComfyUI 0.27.0 frontend 1.45.20.mp4
Shows the issue in the newer/problematic version.

2. ComfyUI - clicks registering - ComfyUI 0.16.3 frontend 1.39.19.mov
Shows the same system using the previous version where clicks register normally.

### Steps to Reproduce

1. Launch ComfyUI 0.27.0 with frontend package 1.45.20.
2. Open a workflow containing normal node widgets, especially a KSampler Advanced node.
3. Click repeatedly on node controls such as:

* control_after_generate
* seed
* steps
* cfg
* sampler/scheduler dropdowns
* numeric input fields
* other widget rows inside the node
4. Observe that some clicks do not register even when clicking directly on the visible widget/control.
5. Repeated attempts may eventually trigger the expected UI response.

Regression comparison:

On the same system, I launched a previous ComfyUI install, ComfyUI 0.16.3 with frontend 1.39.19, and the issue does not occur there. In the previous version, clicks register normally.

I am attaching both screen recordings so the difference is visible.

### Debug Logs

```powershell
Problematic version where issue occurs:

ComfyUI version: 0.27.0
comfyui-frontend-package version: 1.45.20
comfy-aimdo version: 0.4.10
comfy-kitchen version: 0.2.16
comfyui-workflow-templates version: 0.11.1
comfyui-embedded-docs version: 0.5.6

Platform: Windows
OS: Windows 11
Python version: 3.13.11
PyTorch version: 2.10.0+cu130
GPU: NVIDIA RTX A4500
NVIDIA driver: 582.16
Total VRAM: 20470 MB
Total RAM: 28652 MB
VRAM mode: NORMAL_VRAM
Device mode: cudaMallocAsync

Relevant warnings from the problematic version startup log:

[rgthree-comfy] ComfyUI's new Node 2.0 rendering may be incompatible with some rgthree-comfy nodes and features, breaking some rendering as well as losing the ability to access a node's properties...

[DEPRECATION WARNING] Detected import of deprecated legacy API: /scripts/ui/components/buttonGroup.js
[DEPRECATION WARNING] Detected import of deprecated legacy API: /scripts/ui.js
[DEPRECATION WARNING] Detected import of deprecated legacy API: /extensions/core/clipspace.js
[DEPRECATION WARNING] Detected import of deprecated legacy API: /extensions/core/widgetInputs.js
[DEPRECATION WARNING] Detected import of deprecated legacy API: /scripts/ui/components/button.js

Known-good previous version where issue does not occur:

ComfyUI version: 0.16.3
ComfyUI frontend version: 1.39.19

Platform: Windows
OS: Windows 11
Python version: 3.13.11
PyTorch version: 2.10.0+cu130
GPU: NVIDIA RTX A4500
NVIDIA driver: 582.16
Total VRAM: 20470 MB
Total RAM: 28652 MB
VRAM mode: NORMAL_VRAM
Device mode: cudaMallocAsync

The full terminal logs can be provided if needed, but I have omitted local file paths from this ticket.
```

### Other

This appears to be a regression because the same system does not show the issue in ComfyUI 0.16.3 / frontend 1.39.19, but does show the issue in ComfyUI 0.27.0 / frontend package 1.45.20.

Both installs include custom nodes, so the mere presence of custom nodes does not appear to be enough to trigger the issue. However, the problematic log includes warnings related to Node 2.0 rendering compatibility and deprecated frontend APIs, so those may be relevant.

Some custom nodes/extensions loaded in the problematic version include:

```text
ComfyUI-Manager
rgthree-comfy
comfyui-easy-use
ComfyUI-KJNodes
ComfyUI-LTXVideo
ComfyUI-WanVideoWrapper
comfyui-videohelpersuite
ComfyUI-GGUF
comfyui-impact-pack
comfyui_controlnet_aux
RES4LYF
radiance
ComfyUI-Crystools
ComfyUI_essentials
comfyui-custom-scripts
ComfyUI-AudioLoopHelper
ComfyUI-RBG-SmartSeedVariance
ComfyUI-mxToolkit
ComfyUI-Krea2T-Enhancer
ComfyUI-NKD-Sigmas-Curve
```

Suggested attachment filenames:

```text
ComfyUI - clicks not registering - ComfyUI 0.27.0 frontend 1.45.20.mp4
ComfyUI - clicks registering - ComfyUI 0.16.3 frontend 1.39.19.mov
```

Reproduce the regression in ComfyUI 0.27.0 with frontend package 1.45.20, especially on KSampler Advanced widget rows, and compare it with ComfyUI 0.16.3 and frontend 1.39.19. Start by testing with custom nodes disabled, then inspect node-widget hit testing and the deprecated frontend paths listed in the report. Done means visible controls consistently respond to direct first clicks without affecting normal canvas interaction.

Written by the indexing model from the issue text.