Clicking field titles causes focus to jump to first input and scroll to top
This is a known bug in Sanity Studio that has affected multiple users with complex schemas containing fieldsets. When you click on the label or description of fields within collapsed fieldsets, Studio incorrectly focuses the first input (usually the title field) and scrolls to the top instead of focusing the field you actually clicked on.
What's happening
Based on reports from the Sanity community, this issue particularly affects documents where:
- You have multiple fieldsets (especially 2 or more)
- Some fieldsets are configured with
collapsed: trueby default - The fieldset rendered last in the document tends to have the most focus issues
The problem is especially frustrating with radio buttons and other controls where users naturally expect to click the label to interact with the field - instead, focus jumps to the top of the page.
History and fixes
This bug was partially addressed in Sanity Studio v2.1.4 (released January 2021), which fixed "form would scroll to top when first focusing a child of a nested field." However, as reported in the community thread, some users continued experiencing focus issues even after that update, particularly with:
- Fields in the second or last fieldset when multiple fieldsets are collapsed by default
- Clicking labels of radio buttons and other controls within collapsed fieldsets
Potential workarounds
While waiting for a complete fix:
Temporarily disable collapsed state: Set
collapsed: falseon your fieldsets to confirm the issue is fieldset-related. This isn't ideal for UX but helps isolate the problem.Update to the latest Studio version: Run
sanity upgradeto ensure you have the latest patches. The focus behavior has been improved over multiple releases.Reorder fieldsets: If possible, try reordering your fieldsets - the last-rendered fieldset seems most prone to focus issues.
Test with minimal schema: Create a simplified test document with just the problematic fieldsets to isolate whether it's the fieldsets themselves or interaction with other schema features.
Reporting the issue
If you're still experiencing this on the latest Studio version (especially Studio v3 or v4), I'd recommend opening a new issue on the Sanity GitHub repository with:
- Your exact Studio version (
sanity versions) - A minimal reproducible schema showing your fieldset configuration
- Specific steps to reproduce (which field labels cause the jump)
- Whether you're using Studio v2, v3, or v4
The Sanity team has been responsive to these types of UX bugs, and providing clear reproduction steps helps them prioritize fixes for core editing workflows with fieldsets and collapsed sections.
Show original thread14 replies
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.