Playbook editor: render fenced code as coherent blocks - #1290
Merged
Conversation
Contributor
Author
|
Browser parity artifact showing the coherent multiline fenced-code block: |
Merged
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
Rendering model
The TUI paints the block background directly into otherwise-empty frame cells before rendering text. It adds no glyphs or padding, so wrapping, cursor positions, selections, remote offsets, and hit testing stay on the source-stable model from PR #1287. The web keeps one DOM row per source line and uses contiguous full-content-width backgrounds with top corners only on the opener and bottom corners only on the closer.
Regression coverage
Verification
Binary
This change ships in construct. Worktree debug binary: /Users/moon/agentd/.claude/worktrees/playbook-fenced-code-block/target/debug/construct