Repository navigation
fix(web): preserve quote boundaries in restored drafts - #1055
Merged
Merged
Conversation
Upstream divergenceBoth sides are compared with upstream at the in-order tip
Upstream files that start to differ (1)
|
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
incognitojam
force-pushed
the
styal/preserve-message-markdown
branch
from
October 25, 2026 18:05
d05cc08 to
df758ac
Compare
incognitojam
enabled auto-merge (squash)
October 25, 2026 19:12
incognitojam
pushed a commit
that referenced
this pull request
Oct 29, 2026
…ingdotgg#19186) Co-authored-by: Claude Opus 5.5 <[email protected]> Co-authored-by: Julius Marminge <[email protected]> Fork adaptation: The lockfile is regenerated from the fork's dependency graph and uses the fork's existing Tiptap 3.31.4 graph for the new italic dependency. Retain restored-draft normalization and history normalization from the composer-draft-sync feature (including fork PR #1055), alongside upstream's literal underscore rules. (cherry picked from commit bb76f12) Upstream-PR: 19186 Fork-Feature: composer-draft-sync
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.
Problem
A restored or prefilled rich-text value can show a comment outside a quote in the composer, then send it inside the quote. The editor displays parsed blocks while the stored value still lacks the blank Markdown line that separates the comment from the quote; editing the text was required to serialize that separator.
Typing a quote and comment into a new-thread composer already uses the separator fix on main. This PR covers the additional loaded-value path, where text is sent without a further edit.
Change
After applying a controlled rich-text value, persist the editor's serialized document when it differs from the source and that source is still current. Sending a restored draft now preserves the quote boundary already shown in the composer. Plain-text input and literal question answers keep their source text.
Scope and approval
Focused correction to restored/prefilled composer state in the shared web and desktop editor. The existing draft-sync ledger records the restored-value invariant and regression coverage.
Verification
Verified in the isolated web client. Desktop shares the editor; the Electron shell, native mobile clients, and remote/tunnel connections were not exercised. No new browser-console or server errors appeared during the verified sends.
Written by an agent (Codex, gpt-6.1-sol).