magento2: Minicart thumbnail image showing wrong size in frontend which is half of image size in XML file

After upgrading Magento version from 2.3.5-p1 to 2.4.3-p1, I am facing the problem of minicart thumbnail size. I found that in the view.xml file, the width and height of half the size set for the minicart thumbnail shows in the frontend minicart.

Note: It works fine in my old Magento version that the size which is in view.xml file shows the width and height of the size in the frontend.

Preconditions (*)

1. Magento version 2.4.3-p1

Steps to reproduce (*)

Important: By the way, this is the default issue in both Blank and Luma themes.

1. Create any one product and upload the thumbnail image of the product in it.
2. Go to Front End and add product to cart.
3. You will see thumbnail images of the product in the minicart.
4. If you inspect it, the image loads the same size as it would in view.xml but in the upper HTML tag <span class="product-image-container"> takes half width and height attribute and due to that minicart design is breaking and showing small thumbnail image.
5. For example, if you enter the 150x150 width and height in the view.xml file, then it will show 75x75 px inline width and height attributes in the upper <span> HTML tag. <image id="mini*cart_product*thumbnail" type="thumbnail"> <width>75</width> <height>75</height> </image>

Expected result (*)

1. Prodcut item width and height of the <span> tag should be 150px shown which is given in the view.xml file

Actual result (*)

1. It is showing 75x75 px width & height in <span> tag. See above screenshots

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.
• < > Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.