Mobile menu crash on iOS 18.2

[gz-devops]

Preconditions and environment

• Magento 2.4.7-p3
• php 8.3.15
• Varnish 7.5
• Redis 7.0.9
• nginx/1.26.2
• Mysql 8.0.40-31

Steps to reproduce

1. Use a real iphone mobile device or apple official simulator
2. Go to frontend home page or any page
3. Mobile menu with hamburger icon appears
4. Press menu icon and open menu
5. Close menu and scroll down

Expected result

• Scrolling should be fine and all blocks should render

Actual result

• When you scroll a little down all blocks are blank with white page. If you press menu again nothing happens and mobile is stuck there for some time. You need to close tab.

Please check this video

Additional information

• No errors in logs of magento or in Nginx

• When tested with apple simulator and real devices with ios 18.2 issue is there

• When tested with really devices and apple simulator in ios versions 18.1, 18, 17.5 issue is not reproducible.

• When test with windows PC, Android, iPad and Macs everything works fine

• Also tested of course with Magento native menu function and major 3rd party module for main menu. Issue is there

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 @gz-devops. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

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

[gz-devops]

@magento I am working on this

[m2-assistant]

Hi @gz-devops! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[gz-devops]

@magento add to contributors team

[m2-assistant]

Hi @gz-devops! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[gz-devops]

I am closing the issue cause we found the problem. It was coming from server side tags.