-
Notifications
You must be signed in to change notification settings - Fork 9.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
Incorrect displaying Product Image Watermarks on Magento 2.2.5 #16929
Comments
Hi @chizhov13. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
where @chizhov13 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
@magento-engcom-team give me 2.2.5 instance |
Hi @chizhov13. Thank you for your request. I'm working on Magento 2.2.5 instance for you |
Hi @chizhov13, here is your Magento instance. |
@magento-engcom-team yes. I am able to reproduse this issue. Just go to the product view on the store front and look at the result. |
Hello @chizhov13, thank you for your report. |
Hello @chizhov13 |
Hello @ronak2ram thank you for your response. I checked your solution on Magento 2.2.5, everything is okey. But then I have tried to reproduce this bug on Magento 2.1.14 and it still does not work properly. I see that this issue is opened for 2.2.x and 2.3.x. but also need to fix it on Magento 2.1.x |
@ronak2ram thanks it is working now on magento 2.2.4 |
Hi @chizhov13. Thank you for your report. The fix will be available with the upcoming 2.2.7 release. |
…arks on Magento 2.2.5 #17013
Hi @chizhov13. Thank you for your report. The fix will be available with the upcoming 2.3.0 release. |
…t Image Watermarks on Magento 2.2.5 #17623
Summary
Background of Product Image Watermarks is displayed incorrect if it is transparent.
Preconditions
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: