The CSS used for the "Order and Return" widget is incorrect and due to that widget fields are hidden behind the products on frontend

[csvikram44]

Preconditions and environment

• Magento Version - I have seen and reproduced an issue in Magento versions 2.4.4 and 2.4.0
• Orders and Returns Widget - This is the default functionality of Magento that we are showing "Orders and Returns" widget on the front end. I set the admin configuration in my local system to show the "Orders and Returns" widget on the front end and its alignment doesn't seem to be proper. I think the style is not correctly added for the form used in "Orders and Returns".

Steps to reproduce

Example:

1. Navigate to the admin panel
2. Go to Content -> Elements -> Widgets and click on "Add Widget" button to create new widget
3. In the Settings -> Select Widgets Type "Orders and Returns" and Design Theme to "Magento Luma" or "Magento Blank"
4. Save information like "Widget Title", "Assign to Store Views" and "Layout Updates"
5. Select "Layout Updates" to display the widget on the frontend of categories in the sidebar
6. Clean cache and check the frontend

Screenshots:

Expected result

My Suggestion:
I think the CSS that has been used for the form should be removed. Or it can be fixed by using the new CSS for the sidebar widget.

The issue is due to below CSS:
.form.form-orders-search { min-width: 600px; width: 50%; }

Expected result:

Actual result

The problem is due to the below CSS and because of this the width of the widget (Order and Return) is coming more and it hides under the products which can be called an alignment issue.
.form.form-orders-search { min-width: 600px; width: 50%; }

Additional information

No response

Release note

No response

Triage and priority

• 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”.

[m2-assistant]

Hi @csvikram44. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

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

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Lima. 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: 👇

• 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.

[mrtuvn]

you can add custom css like this

.sidebar .form.form-orders-search {width: 100%; min-width: unset;}

for override default

[csvikram44]

verride default

Thanks, @mrtuvn for your reply and we have many solutions for this to fix it. But due to which this issue is coming up and it is not of any use, then it would be right to remove it.

[engcom-Lima]

✔️ Issue confirmed

Issue got reproduced in 2.4-develop branch.

Description: Overlap in the frontend between products && Orders and Returns widget.

Pre-requisite:
Fresh magento 2.4-develop should be installed.
PHP 8.1

Steps to reproduce:

1. Navigate to the admin panel
2. Go to Content -> Elements -> Widgets and click on "Add Widget" button to create new widget
3. In the Settings -> Select Widgets Type "Orders and Returns" and Design Theme to "Magento Luma" or "Magento Blank"
4. Save information like "Widget Title", "Assign to Store Views" and "Layout Updates"
5. Select "Layout Updates" to display the widget on the frontend of categories in the "sidebar".
6. Clean cache and check the frontend of guest customer.

Expected result: Orders and Returns widget should be displayed in the frontend without overlap.
Actual result: There was overlap between products from Orders and Returns widget.
Screenshots:

Hence, confirming this issue.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6014 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.