Repository navigation
Render Markdown in browser chat messages - #33
Merged
storytellerF merged 1 commit intoOct 3, 2026
Merged
Conversation
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
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.
Summary
Render Markdown in browser chat messages instead of showing formatting syntax as plain text. Support headings, emphasis, lists, quotes, fenced code, tables, links, and images while keeping the copy button's output as the original Markdown.
Parse each incoming message once in the existing Worker with a locally bundled markdown-it 15.0.2. Raw HTML stays disabled, dangerous URL validation remains enabled, and sender-supplied HTML fields are ignored. Links open separately with
noopener noreferrer. Include upstream license notices and a reproducible vendoring script.Keep long messages inside the scrollable message log so the composer stays visible on phones. Code blocks and tables scroll horizontally without widening the page.
This builds directly on merged PR #32 and contains only the Markdown increment. No CI workflow changes.
Validation
Completed locally during implementation:
:app:testDebugUnitTest --tests '*WebPagesTest'passed, including real Ktor serving of the parser modules with JavaScript MIME types.:app:assembleDebugpassed.Browser interaction checks use mock HTTP/SSE/WebSocket endpoints; real Ktor resource serving is checked separately on the JVM. Installed-device end-to-end testing and Alpha/Release builds were not run for this change.