Skip to content

docs: correct FIDELITY.md -- block-in-inline promotion closed in round 38 - #290

Merged
tannevaled merged 1 commit into
mainfrom
docs/stale-known-gaps-blockinline
Oct 18, 2026
Merged

tannevaled merged 1 commit into
mainfrom
docs/stale-known-gaps-blockinline

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

Summary

  • "Known gaps" claimed a block-level element nested under an inline-context ancestor (the <react-partial>/votearrow pattern) was unfixed and "comparable in scope to Shadow DOM" -- round 38 (engine#118) actually closed this on 2026-09-05, with passing regression tests still green on current code.
  • Corrects both the block-in-inline entry and the inline-flex entry that cross-referenced it with the same stale claim.

Test plan

  • Docs-only change. Confirmed layout/blockinline_test.go's regression tests (TestFlexContainerUnderUnstyledInlineElementGetsRealLayout, TestBlockBreakResetsPendingWhitespace, etc.) all still pass before writing the correction.

…d 38

"Known gaps" kept saying a block-level element nested under an inline-
context ancestor (the <react-partial>/votearrow pattern) was
flattened into plain text and "not attempted", citing architecture
"comparable in scope to Shadow DOM". Round 38 (2026-09-05, engine#118)
actually built this (InlineItem.BlockBreak + placeInlineSegments,
following CSS 2.1 Section 9.2.1.1), with passing regression tests
still green on current code -- confirmed live while drafting a plan
to implement what turned out to already exist.

The inline-flex entry repeated the same stale cross-reference ("needs
the same mechanism this engine has never had"), even though its own
opening sentence already said the mechanism existed and was wired in
at round 148. Corrected both to point at the actual closing round
instead of each other's now-six-week-old citation.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit 3e4b0b8 into main Oct 18, 2026
7 checks passed
@tannevaled
tannevaled deleted the docs/stale-known-gaps-blockinline branch October 18, 2026 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant