Repository navigation
Publish measured PDF renderer comparison with complete evidence - #43
Merged
Merged
Conversation
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.
Developers comparing PDF renderers can now inspect the outputs and reproduce the measurements. Publish a shared-input comparison of Fullbleed 2.5.6, WeasyPrint 70.0, and Playwright 1.63.0/Chromium, with complete raw evidence and clearly scoped findings.
The report includes all 315 latency samples, separate memory measurements, nine representative PDFs, every retained output, and the initial font/PATH diagnostics. It explicitly reports Chromium's faster warm ledger, WeasyPrint's smaller files, and Chromium's extra ledger page alongside Fullbleed's startup and other warm-latency results. Source is merged in fullbleed-engine/fullbleed-official#37.
Validation: 414 PDF outputs qualified; all 22 representative page images matched the visually inspected qualification images; both archives passed their member hashes; all table statistics were independently recomputed; and all nine representative PDFs passed fresh reader checks on Windows. The page passed local Chrome checks at 1440, 390, and 320 pixels, actual ZIP download hashes, and all nine PDF HTTP responses. Strict docs build and link checks passed using unchanged deployed playground build assets locally; CI rebuilds those assets from source.