Accessibility: Focus moves to the wrong trigger when using "Open programmatically"…
- User
Accessibility: Focus moves to the wrong trigger when using "Open programmatically" buttons
Current behavior
In the Alert Dialog, Dialog and Popover components, there is a variant that includes the option to use multiple triggers to open the dialogs. When using the "Open Programmatically" button to open the dialog/popup, then closing it, focus moves to a different control than the one that triggered the dialog/popup.
See:
- [Alert Dialog: Controlled mode with multiple triggers](https://base-ui.com/react/components/alert-dialog#controlled-mode-with-multiple-triggers
- Dialog: Controlled mode with multiple triggers
- Popover: Controlled mode with multiple triggers
This could cause failures against WCAG 2.2 Success Criterion 2.4.3 Focus Order when implemented.
Expected behavior
Keyboard focus should move back to the originating control (if available) when closing a dialog as long as a page refresh or redirection is not triggered.
If the control is no longer available, focus should move next to that originating control's position in the DOM.
Reproducible example
- Go to [Alert Dialog: Controlled mode with multiple triggers](https://base-ui.com/react/components/alert-dialog#controlled-mode-with-multiple-triggers
- Using keyboard, move focus to the "open programmatically" button
- Press Enter to activate the control and open the dialog
- Press Esc or activate the close button to close the dialog
- Note focus has moved back to the "Delete" button and not the "open programmatically" button as expected.
Base UI version
v1.2.0
Which browser are you using?
Chrome 145.0.7632.76
Which OS are you using?
Mac OS Tahoe 26.2
Which assistive tech are you using (if applicable)?
Keyboard
Additional context
Recommend keeping track of focus and returning it to the originating control.
Interface
No new interfaces are introduced.
- Assistant
I'll investigate how focus restoration works in Dialog, Alert Dialog, and Popover when multiple triggers are used, starting with the controlled-mode demos and focus-management code.
- Assistant
Implementing the fix in
FloatingFocusManager: when closing, prefer the element that had focus at open time overdomReferenceif it isn't a registered trigger. - Assistant
Implementing the fix and adding a regression test.
- Assistant
Reverting the broad
FloatingFocusManagerchange and implementing a targeted fix via the popup store. - Assistant
Updating focus return to fall back when the programmatic opener is no longer in the DOM.
- Assistant
Fixed focus restoration when a dialog/popover is opened programmatically while a different trigger is designated as active.
Root cause
In controlled mode with multiple triggers, opening via an external button (e.g. "Open programmatically") sets
triggerIdto aDialog.Trigger/Popover.Triggerid. On close, focus was returned to that active trigger (domReference) instead of the control that actually opened the popup.Fix
-
focusReturnTargetin popup store — When a popup opens, if the focused element differs from the active trigger, that element is stored as the focus return target. -
useFocusReturnTargethook — Added inDialog.RootandPopover.Root(covers Alert Dialog too via shared dialog root). -
resolvePopupFinalFocushelper — Used byDialog.Popup,Drawer.Popup, andPopover.Popupto return focus tofocusReturnTargetwhenfinalFocusis not explicitly set. If the opener is no longer in the DOM, it falls back to the default trigger behavior.
Tests
DialogPopup.test.tsx: returns focus to the programmatic opener when the active trigger differsDialogRoot.detached-triggers.test.tsx: Chromium test for the same scenario (requires browser env)
Normal trigger clicks are unchanged: focus and active trigger are the same element, so
focusReturnTargetis not set and focus still returns to the trigger. -
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →