Repository navigation
FocusScope skips a Tab stop after an exiting sibling scope unmounts #10593
Description
🐛 Bug Report
When one overlay opens another before it finishes closing, unmounting the first overlay can break keyboard navigation in the second. One Tab skips a focusable element. On a fresh opening, Shift+Tab can move focus outside the second overlay even though its FocusScope has contain enabled.
The two scopes are siblings under an outer FocusScope in the React component tree. The second scope stays mounted, and focus is already inside it when the first scope unmounts.
🤔 Expected Behavior?
Removing the closing overlay should not change keyboard navigation in the overlay that remains open. Tab should move to the next focusable element, and Shift+Tab from the first element should wrap to the last. Focus should stay within the containing scope.
😯 Current Behavior
After the closing overlay unmounts, the first Tab skips the next button. Testing Shift+Tab instead on a fresh opening moves focus to a button outside the remaining overlay.
💁 Possible Solution
Change FocusScope cleanup so that it resets activeScope only when the scope being removed is itself active. If the active scope is a descendant that remains mounted, preserve it while removing its ancestor and reparenting it.
In the cleanup condition, this means replacing scopeRef === activeScope || isAncestorScope(scopeRef, activeScope) with scopeRef === activeScope. The isAncestorScope helper remains in its other call sites.
The added forward and reverse Tab regression tests fail without this change and pass with it. The existing whole-subtree focus restoration test also passes unchanged.
🔦 Context
Selecting a menu item opens another popover. The menu briefly remains mounted while the new popover opens. Once the menu unmounts, the first Tab in the new popover skips a button.
🖥️ Steps to Reproduce
https://codesandbox.io/p/sandbox/xfgnvy
- Open the standalone preview.
- Focus Open menu and press Space. Wait for focus to reach Choose date and time.
- Press Space again, then wait for the first overlay to fade out. Focus is now on September, the first enabled button in the second overlay.
- Press Tab once. Expected: 2026. Actual: Next month, skipping 2026.
- Reload and repeat steps 2–3. Press Shift+Tab instead. Expected: Next month (wrap to the last button). Actual: Open menu, outside the second overlay.
After the closing overlay unmounts, a single Tab skips a button in the overlay that remains open, even though its FocusScope still has contain enabled.
Version
react-aria@3.52.1
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
macOS 26.4.1, arm64
🧢 Your Company/Team
No response
🕷 Tracking Issue
N/A
Activity
dvd233 commentedon Sep 10, 2026
Thanks for the detailed reproduction. I’m going to work on this by adding forward and reverse Tab regression coverage for the surviving sibling scope, and by limiting the cleanup reset to the scope that is actually active. I’ll also keep the existing whole-subtree unmount coverage in the focused test run.
snowystinger commentedon Sep 12, 2026
Is the codesandbox representative of how you've actually built this? Or are you using RAC Modal/Popover? I'm asking because the FocusScope used by those components applies some extra logic when they are exiting
react-spectrum/packages/react-aria/src/overlays/Overlay.tsx
Line 78 in 4693fcc
randomspells commentedon Sep 14, 2026
Hi! The application uses custom components (modal and popover) built on
FocusScope. The reproduction uses simplified versions of those components, withcontainset totruewhile open andfalsewhen closing.snowystinger commentedon Sep 15, 2026
If you stop
containing during the animation out, does it work as expected?randomspells commentedon Sep 15, 2026
No, the menu already has
contain={false}while it fades out, but Tab skips a button after the menu disappears.