Troubleshooting mobile scrolling issue in Sanity Studio

I understand how frustrating mobile scrolling issues can be in Sanity Studio. While I can't find specific documentation about this being a known issue with iOS Safari or Firefox, here are some practical troubleshooting steps that might help:

General Troubleshooting Steps

1. Update Your Sanity Studio Package

Make sure you're running the latest version of Sanity Studio, as updates often include bug fixes and improvements:

npm install sanity@latest

After updating, restart your dev server. Note that Studio v4 requires Node.js 20+.

2. Clear Browser Cache & Test in Incognito

Mobile browsers can cache problematic assets. Try:

• Clearing Safari's cache (Settings → Safari → Clear History and Website Data)
• Clearing Firefox mobile site data for your Studio URL
• Testing in private/incognito mode to rule out cache issues

3. Check for Custom CSS Conflicts

If you've added custom CSS to your Studio configuration, look for styles that might interfere with mobile scrolling:

• overflow: hidden on body or container elements
• position: fixed without proper height constraints
• -webkit-overflow-scrolling properties
• Custom touch-action CSS rules

4. Test on Hosted Studio

If you're running Studio locally, try accessing your hosted Studio at your-project.sanity.studio to see if the issue persists. This helps determine if it's a deployment-specific problem.

5. Check Browser Console for Errors

Open the mobile browser's developer tools (if available) or use remote debugging to check for JavaScript errors that might be preventing normal scrolling behavior.

If These Don't Work

Since this isn't a widely documented issue, it would be helpful to gather more information:

• Which Sanity Studio version are you running? (check package.json)
• Does this affect all pages in Studio or specific document types?
• Are there any custom plugins installed?

Consider reaching out to Sanity's support or posting in the Sanity Community Slack with these details, as the team can investigate whether this is a browser-specific bug that needs addressing.