Comfy-Org / Comfy-Org/ComfyUI

<<SOME TEXT>> in string/multistring node outputs as <> in preview any text node

Open
#11,097 1 comment 0 reactions 0 assignees View on GitHub
Potential Bug
Dominant language
Python
Stars
133k
Forks
15.7k
Avg merge
1d 6h
Merged PRs (30d)
155

Description

### Custom Node Testing

- [ ] 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

Using special characters (e.g., `<>`) in a string or text node should display with the correct output in the Preview as Text (previously Preview Any?) node.

### Actual Behavior

Entering `<>` in a string or text node and connecting the output to a Preview as Text node shows as `<>`. Changing it to `<< SOME TEXT >>` actually does work correctly.

### Steps to Reproduce

Create a workflow with only two nodes: string and preview as text.

Add `<>` as the string.

Run.

View `<>` as the displayed output in the Preview as Text node.

### Debug Logs

```powershell
---
```

### Other

I haven't tested further to see how other special characters (or combinations) are handled, but hopefully this does not suggest an injection-type vulnerability here.

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue with a two-node workflow containing a string node and a Preview as Text node, using `<>` as the input. Trace how the Preview as Text output handles that input and verify that the displayed result preserves the original special characters rather than collapsing to `<>`.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.