Magento2: Thumbnail product image in checkout page order summary too big

[mrtuvn]

Preconditions (*)

1. 2.4.0
2. sample data installed

Steps to reproduce (*)

1. Add product to cart
2. Go to checkout page

Expected result (*)

1. [Screenshots, logs or description]
2. Image size idealy will be 75x75

Actual result (*)

1. [Screenshots, logs or description]
2. Image size 150x150

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] Severity: S0 _- Affects critical data or functionality and leaves users without workaround._
• [ ] Severity: S1 _- Affects critical data or functionality and forces users to employ a workaround._
• [ ] Severity: S2 _- Affects non-critical data or functionality and forces users to employ a workaround._
• [ ] Severity: S3 _- Affects non-critical data or functionality and does not force users to employ a workaround._
• [x] Severity: S4 _- Affects aesthetics, professional look and feel, “quality” or “usability”._

[m2-assistant[bot]]

Hi @mrtuvn. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

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

[m2-assistant[bot]]

Hi @ajijshekh123. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

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

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[ajijshekh123]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @ajijshekh123, here is your Magento instance.
Admin access: https://i-28634-2-4-develop.instances.magento-community.engineering/admin_7d74
Login: 7458527a Password: 985982f5301b
Instance will be terminated in up to 3 hours.

[ajijshekh123]

Hello @mrtuvn,
This issue is reproduced on Magento 2.4 Instance.
See attached the screenshot:

Thanks.

[magento-engcom-team]

:white_check_mark: Confirmed by @ajijshekh123
Thank you for verifying the issue. Based on the provided information internal tickets MC-35036 were created

Issue Available: @ajijshekh123, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[sdzhepa]

Hello @mrtuvn
fyi: @ajijshekh123

Thank you for your report and confirmation!

Occasionally, I found this bug was found and reporter into internal Jira during regression before 2.4.0
The bug has been fixed in delivered into the internal 2.4.0 branch (not publicly available)

• Fix has been done and delivered in the scope of MC-34950
• Internal PR: https://github.com/magento/magento2ce/pull/5757

Changes from the internal branch are not synced yet with the public 2.4-develop branch. But it will be soon. I suppose it should be the same as here https://github.com/magento/magento2/pull/28546/

I provide details/commits here as soon as it will be available in 2.4-develop

[m2-assistant[bot]]

Hi @sdzhepa. 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.
  
  

• 1. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
• 1. 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.

[ajijshekh123]

Thanks for the information @sdzhepa

[sdzhepa]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @sdzhepa. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @sdzhepa, here is your Magento instance.
Admin access: https://i-28634-2-4-develop.instances.magento-community.engineering/admin_3d7d
Login: 96540529 Password: b117d394aa9a
Instance will be terminated in up to 3 hours.

[sdzhepa]

Hello @mrtuvn
cc: @ajijshekh123

The branches have been synced. And this fix for the issue is available now
Issue can be closed.