Affine: keep libvips' native background instead of forcing :black to get alpha-aware fill#205
Merged
kipcole9 merged 2 commits intoJun 30, 2026
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
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.
Image.affine/3,Image.translate/4andImage.shear/4no longer inject a default:backgroundof:black. When:backgroundis omitted, libvips keeps its own native fill, which is transparent on images with an alpha band, opaque black otherwise.:backgroundoption text to document the native default ("transparent for images with an alpha band, black otherwise") in place of "The default is:black."## Partially-transparent backgroundssection like in Expose:interpolateand route:backgroundthroughImage.Pixel.to_pixel/2inImage.rotate/3#204.I think this is more expected/ergonomic? An oversight on my part in #202.