Magento 2.4.4 frontend menu mobile

[fmineo]

Preconditions (*)

1. PHP 8.1
2. Magento 2.4.4 (installed via composer create-project)
3. No sample-data, all defaults.

Steps to reproduce (*)

1. Create a category with a subcategory
2. Go to frontend on mobile device (Vertical mode)

Expected result (*)

1. We should be able to open submenu categories dropdown through the menu.

Actual result (*)

1. We can only see the "top-level" categories, and not the subcategories.
2. If rotate the device in horizontal mode and again in vertical you will able to open the subcategory menu.

---

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

[m2-assistant[bot]]

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

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

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack 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.

[m2-assistant[bot]]

Hi @engcom-Hotel. 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.

[engcom-Hotel]

@magento give me 2.4.4 instance

[magento-deployment-service[bot]]

Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Hotel, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Hotel]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Hotel, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[andrewbess]

@magento give me 2.4.4 instance with env PHP 8.1

[magento-deployment-service[bot]]

Hi @andrewbess. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @andrewbess, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Hotel]

Hello @fmineo,

Thanks for your report and collaboration!

We have tried to reproduce the issue in Magento 2.4.4 but for us, the issue is not reproducible. Please find attached the below screencast for reference:

https://user-images.githubusercontent.com/51681618/164174602-800d153b-0163-4cba-b938-ee2abb6ea3bf.mov

Let us know in case we have missed anything.

Thanks

[fmineo]

Hello @engcom-Hotel,

Thanks for your support!

As I specified, the device must be in "portrait mode" (held vertically) and not horizontally as you showed in the video.

I am also attaching a video trying to be clearer:

https://user-images.githubusercontent.com/5881339/164190034-8f93a4a3-2240-49a2-9090-2bb464e212ba.mp4

Hope it helps.

Thanks

[slavvka]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @slavvka. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @slavvka, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[slavvka]

@magento give me test instance

[magento-deployment-service[bot]]

Hi @slavvka. Thank you for your request. Comments like @magento give me test instance are intended for instance deployments on Pull Requests. Please use comment like: @magento give me 2.4-develop instance to request an instance on an issue.

[slavvka]

@magento give me 2.4.4 instance

[magento-deployment-service[bot]]

Hi @slavvka. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @slavvka, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[slavvka]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @slavvka. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @slavvka, here is your Magento Instance: https://a2f056b41f368c1630574a4ca609d88e.instances.magento-community.engineering Admin access: https://a2f056b41f368c1630574a4ca609d88e.instances.magento-community.engineering/admin_871a Login: 2dbda570 Password: 6b180a554389

[fmineo]

The issue also occurs in the Magento Instance above.

[engcom-Hotel]

Hello @fmineo,

Thanks for the report & collaboration!

We have tried again to reproduce the issue in Chrome's device toolbar and in a mobile device. The issue is reproducible for us with the given steps.

Hence confirming this issue.

Thanks

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-2907 is successfully created for this GitHub issue.

[m2-assistant[bot]]

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

[github-jira-sync-bot]

:x: You don't have permission to export this issue.