Repository navigation
Honor word-break and overflow-wrap in retained text layout - #788
Merged
Merged
Conversation
This was referenced Sep 20, 2026
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 and result
WebScene wrapped retained text only at whitespace, so unchanged Code OSS long tokens overflowed Markdown preview, dialogs, notifications, hovers, hints, quick input, suggestions, REPL/debug surfaces, editor placeholders, comments, and chat/session UI even when their CSS requested word breaking.
This adds
word-break,overflow-wrap, and theword-wrapalias across native/managed property metadata, cascade/CSSOM, inherited cold style state, UTF-8 safe retained fragmentation, fallback line wrapping, and min-content sizing. Long tokens now break at code-point boundaries while selection/highlight byte ranges remain ordered.Closes #787. Parent epic: #235.
Quality and performance gates authored
docs/validation/code-oss-word-breaking-787.md.Validation status
No build, test, WPT run, benchmark, visual comparison, package run, or CI result was executed under the current fast implementation instruction. Evidence is zero; the authored gates remain for consolidated qualification.