feat(text): flow paragraphs through ordered columns (11.18 slice) - #72
Open
thejustinwalsh wants to merge 2 commits into
Open
feat(text): flow paragraphs through ordered columns (11.18 slice)#72thejustinwalsh wants to merge 2 commits into
thejustinwalsh wants to merge 2 commits into
Conversation
ParagraphContentBox gains columns { count, gap }, mapping the public
Text onto the engine's proven ordered multi-region flow: side-by-side
region rectangles inside the exact content-box width, filled in order
without balancing. The column height is the flow signal, so columns
require an exact width and a bounded height, rejected loudly at
construction; column zero keeps the paragraph's region id so
single-column request bytes are unchanged. The editorial workload
becomes a real page: a single-measure justified lede over a body
flowing through two justified columns, batching to three draws over
869 glyphs. Red-green through the real engine: half-height columns
push the tail into the second region, the block extent stays inside
the column height, and both invalid combinations throw. The drop-cap
exclusion surface stays with 11.18 proper. Also corrects the wasm
budget comment: cross-host variance is byte-different equal-length
builds, not gzip nondeterminism.
size-limit report 📦
|
thejustinwalsh
marked this pull request as ready for review
August 14, 2026 02:42
# Conflicts: # docs/packages/benchmarks.md # docs/packages/glyph.md
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
1 participant
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.
What
An 11.18 slice pulled forward on demand:
ParagraphContentBoxgainscolumns { count, gap }, mapping the publicTextonto the engine's already-proven ordered multi-region flow — side-by-side region rectangles inside the exact content-box width, filled in order without balancing.Contract
set().Evidence
Red-green through the real Wasm engine: at the exact column measure, halving the reference height pushes the tail of the text into the second region, the columned block extent stays inside the column height with no overflow, and both invalid combinations throw. The editorial workload becomes a real page — one single-measure justified lede over a body flowing mid-sentence through two justified columns — settling in the presentation probe at three draws (lede + one clipped draw per column) over 869 glyphs at 120 FPS. Full package and benchmark checks green; three-runtime budget re-priced (+1.7 KB raw of geometry derivation and validation).
Also corrects the wasm budget comment from the review closure: cross-host size variance is byte-different equal-length builds (different sha256, same source), not gzip nondeterminism.