Skip to content

[Issue] Fixed conflicting styles for product image container in different listings at the same page #31526

Open
@m2-assistant

Description

@m2-assistant

This issue is automatically created based on existing pull request: #31473: Fixed conflicting styles for product image container in different listings at the same page

Description (*)

This pull requests solves problem when there are two product listing blocks on the same page. Both blocks have at list one common product. And listings have different image sizes for product image.

Related Pull Requests

Can't find related pull requests.

Fixed Issues (if relevant)

Can't find related issue.

Manual testing scenarios (*)

  1. Open product "Crown Summit Backpack" (SKU 24-MB03) to assign up-sell products. Add at list one up-sell product. One of the assigned products must be "Fusion Backpack" (SKU 24-MB02). Save changes.
  2. Create widget "Catalog Product List" via Magento Admin. Assign widget to store view you test. Layout updates settings: display on "Specified page"; page "Catalog Product View"; container "Main Content Top". Widget Options - select at least two product via SKU. One of products must be "Fusion Backpack" (SKU 24-MB02). Save widget.
  3. Clear Magento 2 cache.
  4. Open product page for "Crown Summit Backpack" (SKU 24-MB03) at store front.

image

With old code you can see that "Fusion Backpack" has smaller image than it should.

This pull request fixes it. "Fusion Backpack" will get same size as "Affirm Water Bottle".

Questions or comments

Contribution checklist (*)

  • < ] Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • [ > All automated tests passed successfully (all builds are green)

Metadata

Metadata

Labels

Area: ProductComponent: CatalogIssue: Clear DescriptionGate 2 Passed. Manual verification of the issue description passedIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P2A defect with this priority could have functionality issues which are not to expectations.Progress: ready for devReproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions