openclaw / openclaw/openclaw-windows-node

[Bug] Native chat markdown: text after "——" is truncated; long lines/table cells don't wrap

Open
#1,365 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

impact:ux-friction issue-rating: 🦪 silver shellfish P2
Dominant language
C#
Stars
2.1k
Forks
295
Avg merge
1d 6h
Merged PRs (30d)
99

Description

Environment

  • Windows Hub: v2026.7.1-4 (stable, x64)
  • OS: Windows 10 LTSC 21H2 (build 19044.2311), zh-CN locale
  • Gateway: OpenClaw 2026.8.2 on WSL2
  • Chat content: Chinese (CJK), markdown-formatted agent replies
Bug 1 — text truncated after certain markdown constructs

Agent replies containing the CJK em-dash —— lose everything after it in the native chat window.

Repro: an agent reply containing 快速视图——在聊天框试试,如果没反应告诉我 renders only 快速视图 in Hub chat. The same message renders fully in the web Control UI, so the content is intact server-side — this looks like a native renderer issue.

Bug 2 — long lines don't wrap

Long single-line text (especially inside markdown table cells) does not wrap to the window width in the native chat window; lines appear cut off. The same content wraps correctly in the web Control UI.

Expected: native chat renders markdown at parity with the web Control UI.
Actual: truncation after ——; no wrapping of long lines/table cells.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named; start by locating the native chat markdown renderer and comparing its handling with the web Control UI. Reproduce the CJK em-dash truncation and long-line/table-cell cases, then verify that native rendering preserves all text and wraps long content like the web UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.