From 603a1d1755c8794a0a3642efecdbad66851ac780 Mon Sep 17 00:00:00 2001 From: krflol Date: Wed, 7 Oct 2026 21:20:04 -0500 Subject: [PATCH 1/2] Document the border-image release follow-up --- docs/guides/css-corpus.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/guides/css-corpus.md b/docs/guides/css-corpus.md index 888378a..189f7f4 100644 --- a/docs/guides/css-corpus.md +++ b/docs/guides/css-corpus.md @@ -13,6 +13,8 @@ or WeasyPrint versions. **The full run completed with 1,616 PASS, 27 FAIL, and 19 REFERENCE-DISPUTED across 1,662 fixtures.** +These are the retained 2.5.14 results. A [later border-image fix](#border-image-follow-up-in-2515) is available in 2.5.15. + | Verdict | Fixtures | | --- | ---: | | PASS | 1,616 | @@ -85,6 +87,27 @@ that the JSON, Markdown, and HTML identify the same invocation and JSON digest. [Image provenance and hashes](../assets/css-corpus/source.json) | [Upstream MIT license](../assets/css-corpus/IRONPRESS-LICENSE.txt). All failing cases remain in the complete report. +### Border-image follow-up in 2.5.15 + +Fullbleed 2.5.15 fixes the overlapping source slices in the fixture above. +In a complete corpus run of source commit `9ec4f71`, before the version bump, +that fixture changed from FAIL to PASS: **1,617 PASS, 26 FAIL and 19 +REFERENCE-DISPUTED**. Its above-floor page difference fell from 4.30% to 0.24%. +The other 1,661 PDFs were byte-identical to the published 2.5.14 baseline; +there were no new failures or lost passes. The unchanged upstream gate still failed. + +The source candidate's wheel reports 2.5.14; its commit and wheel hash distinguish +it from the published package. This is not a complete corpus run of the final +2.5.15 registry wheel. Fresh public Python and Rust installations passed 21 focused +border-image cases. The original failing input also matched the reviewed source +pixels when the public 2.5.15 Python output was rendered with PDFium. + +[Inspect the source corpus comparison](https://github.com/fullbleed-engine/fullbleed-official/releases/download/v2.5.15/fullbleed-source-9ec4f71-css-corpus-summary.json), +[download its full evidence](https://github.com/fullbleed-engine/fullbleed-official/releases/download/v2.5.15/fullbleed-source-9ec4f71-css-corpus-evidence.zip), +or [read the release verification and reproduction instructions](https://github.com/fullbleed-engine/fullbleed-official/releases/tag/v2.5.15). +The [remaining failures are tracked publicly](https://github.com/fullbleed-engine/fullbleed-official/issues/54). +The tables, failure list and images on this page retain the original 2.5.14 results. + ## Results by category These are fixture counts within this corpus, not percentages of the CSS standard. From df3fb8806383d766554394e6da539ac3f27b4c49 Mon Sep 17 00:00:00 2001 From: krflol Date: Wed, 7 Oct 2026 21:25:40 -0500 Subject: [PATCH 2/2] Specify the Rust SVG feature used in verification --- docs/guides/css-corpus.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/guides/css-corpus.md b/docs/guides/css-corpus.md index 189f7f4..4a749b2 100644 --- a/docs/guides/css-corpus.md +++ b/docs/guides/css-corpus.md @@ -99,7 +99,8 @@ there were no new failures or lost passes. The unchanged upstream gate still fai The source candidate's wheel reports 2.5.14; its commit and wheel hash distinguish it from the published package. This is not a complete corpus run of the final 2.5.15 registry wheel. Fresh public Python and Rust installations passed 21 focused -border-image cases. The original failing input also matched the reviewed source +border-image cases, with Rust's `svg_raster` feature enabled to match the Python +wheel. The original failing input also matched the reviewed source pixels when the public 2.5.15 Python output was rendered with PDFium. [Inspect the source corpus comparison](https://github.com/fullbleed-engine/fullbleed-official/releases/download/v2.5.15/fullbleed-source-9ec4f71-css-corpus-summary.json),