Repository navigation
Fix generated counter labels with Fullbleed 2.5.49 - #64
Merged
Merged
Conversation
krflol
marked this pull request as ready for review
November 1, 2026 02:53
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.
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.