Uh oh!
There was an error while loading. Please reload this page.
feat(app): support bidirectional chat text - #38079
Conversation
The following comment was made by an LLM, it may be inaccurate: The PR #37249 appears in the results, which is already mentioned in the current PR's description as a related PR. Since PR #38079 is the current PR and #37249 is explicitly noted as related (handling rendered Markdown and tables while this PR handles the prompt editor), these are complementary changes rather than duplicates. No duplicate PRs found |
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Issue for this PR
Closes#32726
Related: #35319 and #37249
Type of change
What does this PR do?
Adds
dir="auto"to user-message text and both the legacy and v2 prompt editors.The browser determines direction from the first strong character, so Persian, Arabic, and Hebrew text renders RTL while English remains LTR. Mixed RTL/LTR text continues to use the browser's Unicode bidirectional handling.
This complements #37249, which handles rendered Markdown and tables but was opened before the current v2 prompt input was added.
How did you verify your code works?
session-uitest suite: 75 tests passed.packages/session-uiandpackages/app.Screenshots / recordings
Before/after examples of the RTL rendering issue are available in #35319.
Checklist