-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extend()
background colour changes after composite()
#2858
Comments
It looks like the To fix this, I think we'll need to pass Lines 773 to 776 in 3402656
|
Commit 60adc11 fixes this and adds a test that would previously have failed. Thanks for reporting! |
Fantastic - thanks for the amazing work you're doing with sharp and libvips, @lovell ❤️ |
v0.29.1 now available. |
Are you using the latest version? Is the version currently in use as reported by
npm ls sharp
the same as the latest version as reported bynpm view sharp dist-tags.latest
?Yes.
What are the steps to reproduce?
What is the expected behaviour?
I would think that the square in the center and the extension to the image would have the same colour.
What is the observed behaviour?
The square and the extension has differing colours.
If I specify
premultiplied: true
to the first step of the composite operation, they seem to have the same colour, but not the one I am expecting (#bf1942
).If I do not run the
composite()
operation, the extension has the correct colour.What is the output of running
npx envinfo --binaries --system
?The text was updated successfully, but these errors were encountered: