Inconsistent focus trapping in Rancher modal dialogs

Answer

Rancher 2.x builds modal dialogs with PatternFly's Modal component, which uses focus-trap-react to keep keyboard focus inside the dialog while it is open. Rancher's public documentation does not specify a focus-return policy for modals, and the component does not expose a configuration option to force focus back to the element that opened the dialog. When a modal closes, focus generally follows the browser's default behavior rather than returning explicitly to the trigger.

Confirmed behavior

• PatternFly's Modal activates a focus trap on mount and releases it on unmount.
• Rancher 2.x relies on focus-trap-react for that trap.
• No documented focus-return policy or custom focus-handling option exists in Rancher's public docs.

Likely explanation

• When a second modal opens from inside the first, the trap applies to the topmost modal while the outer modal stays mounted, so its trap can remain active and let focus escape to background content after the inner modal closes.
• The close handler typically does not call focus() on the original trigger element, so focus lands on the close button, the last focused inner element, or the document body instead.

These are likely explanations based on the component stack, not confirmed Rancher-specific behavior. Focus-trap behavior may differ between Rancher 2.x releases, and custom modal wrappers or portal-based libraries can change the focus flow.

Verification steps

1. Open a Rancher page that launches a modal, such as cluster creation.
2. Press Tab and Shift+Tab while the modal is open and confirm focus never leaves the dialog.
3. Close the modal with Esc or the close button.
4. Observe where focus lands. If it stays on the close button or an internal element, Rancher is not returning focus to the trigger.
5. Inspect the rendered Modal in browser dev tools to confirm the PatternFly component is used and check whether the close handler invokes focus() on the trigger element.

Mitigation steps

• Store the trigger element in a ref when the modal opens.
• In the modal's onClose callback, call triggerRef.current.focus() to return focus explicitly.
• For nested modals, ensure the outer modal's close logic runs only after the inner modal has unmounted so no stale trap remains active.

Missing diagnostic detail

Which Rancher 2.x release are you running? Newer builds may have changed the modal stack or added explicit focus-return logic, and the exact version determines whether this is a regression or an unresolved limitation.