Users cannot scroll overlay menu in Safari

[sophie-neale]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

11.4.2

Bug summary

When using Umbraco on Safari browsers the menu overlay can lock in position and I cannot scroll.

Specifics

not.able.to.scroll.mov

Steps to reproduce

In my video you'll see me choose a module and initially I can scroll the overlay, but after I have selected a 'Theme' I am not able to scroll, unless I resize the screen or submit and reopen.

I've only seen this in Safari so far (eg Chrome looks fine)

Expected result / actual result

No response

[github-actions]

Hi there @sophie-neale!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[elit0451]

Hi @sophie-neale 👋

In the video below I tried to reproduce on Safari but I can scroll without an issue. I've tried to show the setup I am using:

SafariScrolling.mp4

Being more specific about your setup could help us reproduce! 🙂

[kjac]

Looks like this issue has gone somewhat quiet. We're going to close it for now. If the issue still persists, please reopen with additional steps to reproduce.