docs(web): document dashboard RTL chat limits#29069
Closed
wesleysimplicio wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Ready for maintainer review. This is docs-only and the current checks are green: docs-site-checks, history, nix ubuntu, and nix macos. Scope remains limited to documenting the existing RTL/complex-script limitation and the API-server workaround path. |
10 tasks
Contributor
Author
|
Closing non-fix PR as requested — mantendo apenas PRs de fix. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Addresses #29047.
Root cause
The detailed rationale from the original PR body is preserved below. This template update keeps the review structure consistent with #29640.
Fix
Why this shape
Issue #29047 reports that Arabic text in the dashboard chat pane appears left-to-right with disconnected letters. Replacing the chat surface is a larger product/design change, and the dashboard currently embeds the real TUI rather than a separate DOM chat implementation. This PR makes the limitation explicit and gives affected users a supported workaround through the documented HTTP API path.
Tests
The original PR body below contains the previous validation notes, commands, or test plan.
No code changes are introduced by this formatting update itself.
Related PRs / issues
Original body
## Related Issue
Addresses #29047.
Type of Change
What changed
The Web Dashboard guide now documents the current RTL and complex-script limitation of the
/chattab. The note explains that the tab renders the real Hermes TUI through xterm.js, which preserves terminal cell layout but does not provide normal browser paragraph direction or glyph shaping for Arabic, Persian, Urdu, Hebrew, and similar scripts.It also points RTL-heavy workflows to the existing OpenAI-compatible API server path, where downstream clients can render messages in normal DOM controls such as
textarea dir="auto"withunicode-bidi: plaintext.Why
Issue #29047 reports that Arabic text in the dashboard chat pane appears left-to-right with disconnected letters. Replacing the chat surface is a larger product/design change, and the dashboard currently embeds the real TUI rather than a separate DOM chat implementation. This PR makes the limitation explicit and gives affected users a supported workaround through the documented HTTP API path.
Duplicate/overlap check
I searched the current open PR queue for direct overlap with
Arabic,RTL,xterm,web dashboard, and#29047before opening this.Related but not duplicate:
How to Test
git diff --check -- website/docs/user-guide/features/web-dashboard.mdnpm --prefix website cinpm --prefix website run buildBuild completed successfully. Docusaurus still reports pre-existing broken link/anchor warnings elsewhere in the docs site; this change does not introduce a new broken link.
Risk
Low. This is a docs-only clarification for an existing limitation and links to an already documented API-server workaround path.
Checklist
Generated by Hermes Turbo