Summary
In the web editor's Comments panel, suggestion cards of kind markdown_insert ("Insert Markdown:") and block_delete ("Delete block:") do not scroll to or highlight their anchor location in the document when clicked — unlike inline replace suggestions, which highlight their text range. Reviewers of long documents cannot tell where a proposed insertion or block deletion applies without reading the anchor block's text and searching manually.
Steps to reproduce
- Create a tmp document with a few paragraphs.
- As an agent, POST a transaction with
suggestion.add_markdown (after_block_id set) and a suggestion.add_block_delete.
- Open the document in the browser, open the Comments panel, click each card.
Actual: the card shows the proposed markdown / struck text, but the viewport does not move and nothing in the document is highlighted; the anchor is invisible to the reviewer.
Expected: clicking a card scrolls to the anchor block and highlights it (for block_delete, ideally the block renders with strikethrough inline, as tracked-changes deletions do in other editors).
Both kinds carry a valid anchor: {blockId, startOffset, endOffset} in GET /review, so the position data exists.
Environment
Report written with the help of an AI agent (Claude Code); happy to provide a repro doc.
Summary
In the web editor's Comments panel, suggestion cards of kind
markdown_insert("Insert Markdown:") andblock_delete("Delete block:") do not scroll to or highlight their anchor location in the document when clicked — unlike inlinereplacesuggestions, which highlight their text range. Reviewers of long documents cannot tell where a proposed insertion or block deletion applies without reading the anchor block's text and searching manually.Steps to reproduce
suggestion.add_markdown(after_block_idset) and asuggestion.add_block_delete.Actual: the card shows the proposed markdown / struck text, but the viewport does not move and nothing in the document is highlighted; the anchor is invisible to the reviewer.
Expected: clicking a card scrolls to the anchor block and highlights it (for
block_delete, ideally the block renders with strikethrough inline, as tracked-changes deletions do in other editors).Both kinds carry a valid
anchor: {blockId, startOffset, endOffset}inGET /review, so the position data exists.Environment
https://quarry.lithos.computer, observed 2026-08-19/20suggestion.add_markdownfor insertions in the first place)Report written with the help of an AI agent (Claude Code); happy to provide a repro doc.