Skip to content

Fix generated counter labels with Fullbleed 2.5.49 - #64

Merged
krflol merged 3 commits into
mainfrom
fix/engine-2-5-29
Nov 1, 2026
Merged

krflol merged 3 commits into
mainfrom
fix/engine-2-5-29

Conversation

@krflol

@krflol krflol commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

A container with numbered children could emit an earlier counter value in ::after. Node 0.9.2 pins the verified Fullbleed 2.5.49 crate, which resolves generated counter text in document order through direct and compiled fixed/reflow rendering. The Workers starter is pinned to the same candidate version.

All 13 source CI jobs passed. The packed package's 59 new cases produce 177 PDFs and 300 pages on both Windows and Linux; independent readers confirm each record's counter sequence, binding identity, heading placement and page counts. All 177 PDF byte sequences match across the two platforms. The actual public 0.9.1 control reproduces 47 incorrect direct cases and 12 healthy controls. An isolated installation of the CI tarball passes the same 177 cases, plus the existing page-font checks. All 82 Python verification tests and the existing installed/browser/native gates pass. Saved evidence is tied to the tarball, WASM and fixture hashes. Fixed bindings paint text separately from static content; raw PDF text-stream order is retained, without a logical reading-order claim.

No local Cargo/native build was performed. Components remain alpha. This is scoped fixture verification, not complete CSS conformance, browser raster parity or independent adoption.

@krflol
krflol marked this pull request as ready for review November 1, 2026 02:53
@krflol
krflol merged commit 5dff327 into main Nov 1, 2026
13 checks passed
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