Repository navigation
Preserve radial-gradient endpoints with Fullbleed 2.5.43 - #60
Merged
Merged
Conversation
krflol
marked this pull request as ready for review
October 29, 2026 11:32
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 radial gradient ending with
gold 100%, blue 100%continues gold outside its ending shape in public Node 0.8.6. Pin published Fullbleed 2.5.43 to preserve the final color and opacity and correct zero-width PDF stitching intervals. Package and adapter metadata advance to 0.8.7; the public API, runtime dependencies and other Cargo pins remain unchanged.Add twelve core-qualified inputs through worker and process isolation. The actual public 0.8.6 tarball reproduces 18 color failures and 20 invalid-stitching cases. The candidate passes all 24 cases and preserves four smooth/repeating controls byte for byte. Saved PDFs, native pixels and independent PDFium pixels match the qualified core reference. Both early-ending controls retain their correct outer colors with corrected bounds.
The release gate requires distinct Linux and Windows evidence tied to the exact packed tarball and WASM hash, plus the calibrated Linux public-package failure control. Five new rejection tests cover incorrect identities, missing or duplicate cases, invalid bounds, and incomplete controls. Existing expected output values and CI gates are preserved.
Local Windows validation passed 106 Node tests, TypeScript configurations, isolated tarball installation, all 414 native/WASI PDF and preview comparisons, 77 Python release-gate tests, and existing paint and preformatted checks. Fresh anonymous Chrome PDF downloads, component editing, previews and styled/unstyled HTML-export checks also passed. The full thirteen-job CI matrix remains required before merge and publication.
The new gradient fixtures cover Node worker/process modes. Existing browser tests remain required; these new fixtures do not claim browser coverage, broad CSS parity or standards conformance. Component authoring remains alpha.