M2 hamburger menu incompatible with recent versions of Android browsers.

n2diving-dgx commented 2 years ago

Preconditions and environment

The "hamburger" menu that is displayed in the upper left hand corner of the Luma theme (and thus any theme derived from the Luma Theme, such as ours) in vertical orientation does not function correctly for navigating to subcategories on Android smartphones. However, on a classic PC desktop with Windows then simply resizing the browser window to very narrow such that the hamburger menu appears, the desktop version does function as expected when the hamburger menu items are moused over and hovered. This issue seems to be a compatibility issue with recent versions of Android only... the theme works as expected on iOS devices. This issue is reproduceable on recent Android smartphones and appears to be independent of the browser used.

Steps to reproduce

(1) Clean installation of M2.4.5 with Luma theme and store sample data. (2) Open the website home page using a recent version of the Chrome browser on an Android mobile device (3) Observe that touching the "hamburger" navigation icon displays the list of store sample data categories

Expected result

Able to navigate to sub-categories using the hamburger menu on Android devices.

Actual result

Using the responsive navigation menu on Android devices, touching those categories which have subcategories (i.e. "WOMEN", "MEN", "GEAR" and "TRAINING") are completely non-functional. Touching those four does not expose a list of the sub-categories, indeed nothing at all happens making it impossible to navigate to those categories and their subcategories using responsive navigation on Android mobile devices with M2.4.5 (and M2.4.4)

Additional information

The issue seems to be that at some point in recent updates, the Magento code that drives responsive navigation has become incompatible with Android based browsers. This issue was reproduced using a Samsung S22+ mobile phone, Android 12, Chrome 104.0.5112.97 and Firefox 98.0.1 as well as some other Android phones and browsers. Although, common iOS browsers on iPhone devices such as Safari, Chrome and Firefox do work as expected. The issue was first reported on our production website following an upgrade to M2.4.5 and Php 8.1, but possibly was present on 2.4.4 and Php 7.4 version.

Release note

No response

Triage and priority

[ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[X] 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] commented 2 years ago

Hi @n2diving-dgx. 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

JKetelaar commented 2 years ago

Same issue here

JKetelaar commented 2 years ago

Fixed with https://github.com/magento/magento2/issues/35329#issuecomment-1139618176

m2-assistant[bot] commented 2 years ago

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