CLIP Text Encode Bug

[razvanab]

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?

The text jumps at the beginning when the cursor is outside the node.

Steps to Reproduce

1. Add a CLIP Text Encode.
2. Put a lot of text so the scroll will appear.
3. Scroll down at the end.
4. Move the cursor outside the node.
5. The node text jumps at the beginning.

How is this affecting you?

Visual/UI issue only

ComfyUI Frontend Version

v1.28.7

Browser

Chrome/Chromium

Console Errors

Logs

Additional Context

Recording.2025-10-16.202304.mp4

OS
Windows 11
Python Version
3.12.12 | packaged by conda-forge | (main, Oct 13 2025, 14:23:59) [MSC v.1944 64 bit (AMD64)]
Embedded Python
false
Pytorch Version
2.8.0+cu128
Arguments
main.py --windows-standalone-build --disable-auto-launch --disable-xformers --use-sage-attention --preview-size 320
RAM Total
31.92 GB
RAM Free
10.29 GB
Devices
Name
cuda:0 NVIDIA GeForce RTX 3050 : cudaMallocAsync
Type
cuda
VRAM Total
8 GB
VRAM Free
6.97 GB
Torch VRAM Total
64 MB
Torch VRAM Free
33.9 MB

┆Issue is synchronized with this Notion page by Unito

[dosubot]

Hi @razvanab! I'm Dosu and I’m helping the ComfyUI_frontend team.

This scroll position reset in the CLIP Text Encode node is a known UI issue affecting all textarea nodes, introduced in v1.4.2. It's likely caused by how focus/blur events are handled in the frontend, specifically in the widget and form components that manage text input and scroll behavior. The suspected culprit is logic in changeTracker.ts and a related pull request (details here).

Recent browser tests confirm that text value is retained after focus changes, but do not explicitly address scroll position restoration (see PR #5819). There isn't a documented workaround yet, but the bug is tracked and may be addressed in future updates.

To reply, just mention @dosu.

---

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

[razvanab]

@dosu
Good to know. Thanks.

[christian-byrne]

I am having a hard time reproducing the issue. By chance, does it go away when you disable custom nodes (e.g., with --disable-all-custom-nodes launch argument

https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled