The display watermark size is incorrect compared to the original watermark images on list product,product page on magento2.3.2

[jordantran93]

Preconditions (*)

1.Magento 2.3.2 community edition
2. Fresh installation, no third party modules

Steps to reproduce (*)

1. Go to Content -> Design->Configuration -> Edit Theme Luma
   https://prnt.sc/o8u05g
   2.set watermark image opacity to 99, image size to 255x68, image position to Bottom/Left, and saved configuration. https://prnt.sc/o8u1py
   3.set small watermark image opacity to 99, image size to 147x38, image position to Bottom/Left, and saved configuration. https://prnt.sc/o8u0fu

Expected result (*)

1. watermark images size same image size uploaded is 147x38 on list page, 255x68 size on product page. https://prnt.sc/o8u3co https://prnt.sc/o8u3hk

Actual result (*)

1. On product page and list product page show watermark smaller than origin watermark uploaded https://prnt.sc/o8u36k https://prnt.sc/o8u3lx
2. with images have size different will show watermark have size different and position also different https://prnt.sc/o8u2wa

[m2-assistant]

Hi @jordantran93. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@jordantran93 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-17914 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[wbeltranc]

#cd19latam

[m2-assistant]

Hi @wbeltranc. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[rschulerdh]

@magento I am working on it

[m2-assistant]

Hi @rschulerdh! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and self-assign the issue.

[m2-assistant]

Hi @rschulerdh. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[mattheo-geoffray]

@magento I am working on it

[m2-assistant]

Hi @mattheo-geoffray! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and self-assign the issue.

[m2-assistant]

Hi @Dnd-Dboy. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[VladimirZaets]

Hi @jordantran93. Thank you for your report.
The issue has been fixed in #25528 by @Krielkip in 2.3-develop branch
Related commit(s):

• 85415eff8ddd81c9b204ec6c093efe49d467ba9e
• 2263d2e9fe2359b86c26dc91597cf50b5a87def4

The fix will be available with the upcoming 2.3.5 release.